Add support for s390x

[Joshua-Beha]

Describe the solution you'd like
While inspecting the helm chart for the secrets-store-csi-driver, I noticed that some of the images required to deploy the secrets-store-csi-driver are not build for s390x. After some further inspection the following images do not support s390x:

• registry.k8s.io/csi-secrets-store/driver:v1.4.6
• registry.k8s.io/csi-secrets-store/driver-crds:v1.4.6

The following images do already support s390x:

• registry.k8s.io/sig-storage/csi-node-driver-registrar:v2.11.1
• registry.k8s.io/sig-storage/livenessprobe:v2.13.1

Anything else you would like to add:
I've started to investigate building the required container images on s390x. It looks like it would require modifying the build automation, specifically the BASE_IMAGE file but I'll need to make sure that the images actually build.

Environment:
s390x Image tag

• Secrets Store CSI Driver version: (use the image tag): v1.4.6
• Kubernetes version: (use kubectl version): v1.29.6 (OpenShift version 4.16.3)

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale