transition `oc adm release new` metadata for operating systems

[cgwalters]

See coreos/coreos-assembler#3153 (comment)

Basically, we should rework oc adm release new to natively search for ostree-container images, instead of having this machine-os thing. Further, I think we should suppport multiple in the release image.

Then we can drop the OCP-specific metadata on the container.

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[travier]

/lifecycle frozen

[marmijo]

We are removing the io.openshift.build.version-display-names and io.openshift.build.versions labels (specifically where the key is set to machine-os) from the RHEL 10-based images.

These labels are currently added by COSA and are consumed by the release controller and oc adm release info. They are responsible for:

• Displaying the machine-os version in release information.
• Driving the RPM diff generation seen on the release controller pages (e.g., the package changes list at the bottom of a release page).

Currently, the release tooling does not support multiple components claiming to be machine-os. Including these labels on both the RHEL 9.6 (current default) and RHEL 10.1+ images causes oc adm release info to emit warnings regarding multiple versions and results in incorrect or conflicted reporting in the release controller.

To unblock the inclusion of RHCOS 10.1+ images in the 4.21 payload immediately without breaking the reporting for the currently supported release (RHEL 9.6), we are removing these labels from the RHEL 10.1+ builds as a stop-gap measure. We will retain them on RHCOS 9.6 to ensure the current presentation remains accurate. A complete solution to enable the tooling to report on both streams simultaneously will be determined later.