Implement multi-arch image building/pushing for registry-operator

[Jdubrick]

Which area is this issue related to?

/area registry

Issue Description

The registry-operator currently can be built for both amd64 and arm64 architectures with the setting of the TARGET_ARCH environment variable at image build. In order to allow users pulling the registry-operator image to take advantage of this multi-arch support we should implement the use of a manifest so that users can pull either amd64 or arm64 built images from quay.io, currently only amd64 is being pulled.

Once the manifest is created and apart of the repository, any automation that is currently building images for this repository and pushing them should be doing so to the manifest to allow for multi-arch pulling.

Below is an example from Red Hat Developer:

# First, initialise the manifest
podman manifest create <image name>

# Build the image attaching them to the manifest
podman build --platform linux/amd64,linux/arm64  --manifest <image name>  .

# Finally publish the manifest
podman manifest push <image name>

Acceptance Criteria

• Manifest implemented for multi-arch support
• Any automations building operator images and pushing to quay.io should be pushing to that manifest

[Jdubrick]

Blocking #1552