AppArmor: support path globs when merging profiles

[mhils]

What type of PR is this?

/kind feature

What this PR does / why we need it:

This PR makes spoc merge understand glob patterns in the profile. This improves the UX when merging automatically recorded profiles into hand-maintained ones:

$ cat demo.yml
apiVersion: security-profiles-operator.x-k8s.io/v1alpha1
kind: AppArmorProfile
spec:
  abstract:
    executable:
      allowedExecutables:
      - /sbin/ip{,6}tables-save
$ cat recorded.yml
apiVersion: security-profiles-operator.x-k8s.io/v1alpha1
kind: AppArmorProfile
spec:
  abstract:
    executable:
      allowedExecutables:
      - /sbin/iptables-save
      - /sbin/ip6tables-save
$ build/spoc merge demo.yml recorded.yml
20:14:27.951272 Merging 2 profiles into /tmp/profile.yaml
20:14:27.951288 Reading file demo.yml
20:14:27.951582 Reading file recorded.yml
$ cat /tmp/profile.yaml
apiVersion: security-profiles-operator.x-k8s.io/v1alpha1
kind: AppArmorProfile
metadata:
  creationTimestamp: null
spec:
  abstract:
    executable:
      allowedExecutables:
      - /sbin/ip{,6}tables-save. # no new entries
status: {}

Which issue(s) this PR fixes:

None

Does this PR have test?

Yes.

Special notes for your reviewer:

Does this PR introduce a user-facing change?

`spoc merge` now combines AppArmor profiles with glob patterns in the first profile.

[k8s-ci-robot]

Hi @mhils. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[saschagrunert]

/ok-to-test

[codecov-commenter]

Codecov Report

Attention: Patch coverage is 84.93976% with 25 lines in your changes are missing coverage. Please review.

Project coverage is 41.42%. Comparing base (11d77f4) to head (72a56c8).
Report is 174 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #2239      +/-   ##
==========================================
- Coverage   45.50%   41.42%   -4.08%     
==========================================
  Files          79      108      +29     
  Lines        7782    15587    +7805     
==========================================
+ Hits         3541     6457    +2916     
- Misses       4099     8664    +4565     
- Partials      142      466     +324     

[ccojocar]

/test all

[saschagrunert]

@mhils please rebase on top of main to get the latest CI fixes in.

[ccojocar]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ccojocar, mhils, saschagrunert

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 [ccojocar,saschagrunert]

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

[mhils]

Looks like CI failure are unrelated to the PR and need a restart. :)