[v0.55.x][git cherry-pick 5c81adc] apparmor: fix parsing beta/alpha version

[hswong3i]

Copied from github.com/moby/moby who already has a fix for it. Tested manually on a Ubuntu 23.10 (beta) VM.

Fixes: #containers/podman/issues/20278

Cherry-pick via v0.55, for CRI-O v1.28.x (see https://github.com/cri-o/cri-o/blob/release-1.28/go.mod#L23)

[rhatdan]

/approve
/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hswong3i, rhatdan

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 [rhatdan]

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

[hswong3i]

Shall we create a hotfix patch release for this, so PR from CRI-O could reference to it?

[hswong3i]

@rhatdan since Kubernetes now coming with https://github.com/kubernetes/kubernetes/releases/tag/v1.29.0-rc.1, so soon we need CRI-O for that accordingly.

Now following PR looks good from CRI-O:

• [main] go get github.com/containers/common@v0.55.5-0.20231119144331-165b7a4dd43c cri-o/cri-o#7496
• [release-1.29] go get github.com/containers/common@165b7a4d cri-o/cri-o#7497
• [release-1.28] go get github.com/containers/common@v0.55.5-0.20231119144331-165b7a4dd43c cri-o/cri-o#7498

Shall we give a hotfix patch release here, so CRI-O next stable release for Kubernetes v1.29.0 could reference it, rather than referencing a specific GIT commit?