Adjust test helper-images push according to arch compatibility

[Davo911]

What this PR does / why we need it:
The test images weren't manifested correctly, so this pushes them in the same manner as the operators.
Push logic now filters per-image supported architectures to avoid publishing broken manifests.
Adds per-image Bazel container_push targets.
Just adjusting which helper image is pushed for what arch.
cdi-func-test-cirros-qcow2 is fine for all, while vcenter-simulator is only for x86.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #3688

Special notes for your reviewer:

Release note:

NONE

[kubevirt-bot]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[kubevirt-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign awels for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[coveralls]

coverage: 58.782% (-0.3%) from 59.076%
when pulling 77e568a on Davo911:test-image-multiarch-manifest
into 4c3dc65 on kubevirt:main.

[Davo911]

/test pull-containerized-data-importer-e2e-hpp-latest

[Davo911]

/retest

[Davo911]

/cc @akalenyu

[Davo911]

A few unsupported images were pushed for arm/s390x, so I added a filter

[Davo911]

For Validation:
https://quay.io/user/tgriedel/

[Davo911]

Found a bug where cdi-func-test-cirros-qcow2 images are published for all arches but only amd64 is included in the manifest

[akalenyu]

For Validation: https://quay.io/user/tgriedel/

I think the cdi repos are private, can't tell if this worked

[Davo911]

@akalenyu
looked into this, seems like this issue was solved by another PR when transitioning to rules_oci

So I only had a small adjustment to the architectural support to offer here, but I could also open up a new PR for this.
--> vcenter is not supported for s390x, while the cirros-qcow is working for all arches

[Davo911]

/retest

[akalenyu]

I don't mind if we pivot the existing PR just make sure to adjust commits/pr desc

[akalenyu]

@akalenyu looked into this, seems like this issue was solved by another PR when transitioning to rules_oci

So I only had a small adjustment to the architectural support to offer here, but I could also open up a new PR for this. --> vcenter is not supported for s390x, while the cirros-qcow is working for all arches

Oh you're right, thanks for checking!

[akalenyu]

I don't mind if we pivot the existing PR just make sure to adjust commits/pr desc

Will you be adjusting the title? otherwise the merge commit is going to look off