Add AppArmor key to quadlet containers

[givensuman]

This addresses #27095 by adding an AppArmor key to .container quadlet files.

Checklist

Ensure you have completed the following checklist for your pull request to be reviewed:

• [ x ] Certify you wrote the patch or otherwise have the right to pass it on as an open-source patch by signing all
  commits. (git commit -s). (If needed, use git commit -s --amend). The author email must match
  the sign-off email address. See CONTRIBUTING.md
  for more information.
• [ x ] Referenced issues using Fixes: #00000 in commit message (if applicable)
• [ x ] Tests have been added/updated (or no tests are needed)
• [ x ] Documentation has been updated (or no documentation changes are needed)
• [ x ] All commits pass make validatepr (format/lint checks)
• [ x ] Release note entered in the section below (or None if no user-facing changes)

Does this PR introduce a user-facing change?

Add AppArmor key to quadlet `.container` files which equates to `--security-opt apparmor=` flag.

[ygalblum]

Thanks for the PR. Small nit

[packit-as-a-service]

[NON-BLOCKING] Packit jobs failed. @containers/packit-build please check. Everyone else, feel free to ignore.

[ygalblum]

You need to run gofmt

[mheon]

Test failures are fixed on main - please rebase and we should be good to merge

[mheon]

/approve
LGTM

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: givensuman, mheon

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mheon]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[Luap99]

Please squash all commits into one given it a proper commit message and add Fixes: #27095 to the commit message body please.

[mheon]

CI failures are unrelated to this PR and fixed on main; please rebase, and that should clear things for merge.

[Luap99]

@givensuman please squash (fixup) the commits into one as mentioned in #27420 (review), we like a proper git history with useful commit messages.
And as @mheon mentioned you will need to rebase as well on main to make the CI happy.

If you don't know how to squash and rebase I am happy to do it or give you instructions on how to.

[givensuman]

@givensuman please squash (fixup) the commits into one as mentioned in #27420 (review), we like a proper git history with useful commit messages. And as @mheon mentioned you will need to rebase as well on main to make the CI happy.

If you don't know how to squash and rebase I am happy to do it or give you instructions on how to.

Lemme know if that did the trick!