Parse apparmor's rsyslogd profile after adding a new config

[lodener]

Description

Due to the presence of apparmor in the noble stemcell, PR #212 was merged to update apparmor's rsyslogd profile. When using that commit as the base for our syslog-release, we ran into an issue where apparmor had already started before the pre-start script finished, preventing it from making use of the added syslog_forwarder config. This PR adds a call to apparmor_parser to parse the rsyslogd profile after copying over the new config.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

Testing performed?

• Unit tests
• Integration tests
• Acceptance tests

Checklist:

• This PR is being made against the main branch, or relevant version branch
• I have made corresponding changes to the documentation
• I have added testing for my changes

If you have any questions, or want to get attention for a PR or issue please reach out on the #logging-and-metrics channel in the cloudfoundry slack

[chombium]

LGTM!

@lodener Thank you very much for the fix.