Add more details and examples for platform configuration

[ashokpariya0]

Enhanced the comments to provide more clarity on how to configure platforms for multi-platform builds.

What this PR does / why we need it:
Enhanced comments to provide more details on setting platforms for multi-platform image builds.
Added examples for configuring PLATFORMS and using the PLATFORM_LIST variable.
Clarified the default behavior (builds based on the host architecture).
Provided options for setting specific platforms or using all to include all supported platforms.

Special notes for your reviewer:
For clarity, the main reason is that we need a new release following the changes made to the publish job in PR:
kubevirt/project-infra#3819.

Release note:

None

[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 phoracek for approval. For more information see the Kubernetes Code Review Process.

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

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

[kubevirt-bot]

Hi @ashokpariya0. Thanks for your PR.

I'm waiting for a kubevirt 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.

[ashokpariya0]

cc @oshoval

[oshoval]

Thanks

For visibility, the real reason is that we need a new release now that the publish job was changed.
We would also need a tag afterwards please

[ashokpariya0]

cc @phoracek

[phoracek]

/approved

[phoracek]

Thanks for the contribution. I have released https://github.com/kubevirt/bridge-marker/releases/tag/0.12.0

[ashokpariya0]

Thanks for the contribution. I have released https://github.com/kubevirt/bridge-marker/releases/tag/0.12.0

@phoracek Thank you so much! I can now see that the multi-platform supported images are available at Quay. I also did a quick sanity check on s390x, and everything looks good to me.
@oshoval I really appreciate all your help, thorough reviews, and attention to detail. Your effort has been invaluable, and I’m grateful for your support.