Add s1122 to supported PowerVS system types

[taliandre49]

What this PR does / why we need it:
This PR updates PowerVS machine validation to include the s1122 system type, which is now available in newer PowerVS zones (e.g. dal14).

Upstream CAPI does not manage region or zone mappings; it is responsible for validating supported machine specifications. Without this change, cluster creation targeting newer zones fails validation due to unsupported system types.

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

Special notes for your reviewer:

• This PR intentionally does not add or modify any region/zone mappings.
• Region and zone awareness (e.g. dal14) is handled downstream by the OpenShift installer.
• This change strictly updates PowerVS system type validation to reflect currently supported offerings.

/area provider/ibmcloud

1. Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
   This PR does not change any image versions.

Release note:

Added support for the s1122 PowerVS system type in machine specification validation.

[linux-foundation-easycla]

• ❌ The email address for the commit (85a14b1, e05da7d) is not linked to the GitHub account, preventing the EasyCLA check. Consult this Help Article and GitHub Help to resolve. (To view the commit's email address, add .patch at the end of this PR page's URL.) For further assistance with EasyCLA, please submit a support request ticket.

[netlify]

✅ Deploy Preview for kubernetes-sigs-cluster-api-ibmcloud ready!

Name	Link
🔨 Latest commit	e05da7d
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-cluster-api-ibmcloud/deploys/6966b610d627af0008f352ff
😎 Deploy Preview	https://deploy-preview-2593.cluster-api-ibmcloud.sigs.k8s.io
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: taliandre49
Once this PR has been reviewed and has the lgtm label, please assign prajyot-parab 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

[k8s-ci-robot]

Welcome @taliandre49!

It looks like this is your first PR to kubernetes-sigs/cluster-api-provider-ibmcloud 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api-provider-ibmcloud has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @taliandre49. Thanks for your PR.

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

Details

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.

[Amulyam24]

Hi @taliandre49, can you please sign the CNCF CLA?

[taliandre49]

Hi @Amulyam24, CNCF CLA currently waiting approval by CLA manager!

[Karthik-K-N]

Hey, Thanks for the PR

Without this change, cluster creation targeting newer zones fails validation due to unsupported system types.

Curious to know How are you creating the cluster, Is it using CAPIBM or any other way. Thanks