Add v1beta2 changes to IBMPowerVSImage

[arshadd-b]

What this PR does / why we need it:

This PR consists of following changes

• Adopt CAPI v1beta2 status changes
• Standardize the controller flow by utilising CAPI provided helper functions
• Removed usage of deprecated github.com/pkg/errors package.

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 #2389

Special notes for your reviewer:

/area provider/ibmcloud

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

Release note:

Add v1beta2 changes to IBMPowerVSImage

[netlify]

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

Name	Link
🔨 Latest commit	7ce6672
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-cluster-api-ibmcloud/deploys/6881a4d707983c0008679085
😎 Deploy Preview	https://deploy-preview-2412.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: arshadd-b
Once this PR has been reviewed and has the lgtm label, please assign mkumatag for approval. For more information see the 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

[k8s-ci-robot]

Hi @arshadd-b. 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.

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.

[Karthik-K-N]

Thanks for the PR, I will take a another look once you addressed the comments.

Overall lets revisit the log statement and make them better.

[Amulyam24]

/ok-to-test

[arshadd-b]

Image queued

Image Importing

Image Ready

[Amulyam24]

Overall LGTM! minor comments added

[Amulyam24]

Can you share why we need both of these conditions?

[arshadd-b]

In conditions in v1beta2 we have set two conditions one is ready and one is imageReady

  v1beta2:
    Conditions:
      Last Transition Time:  2025-07-16T13:45:25Z
      Message:               * ImageReady: ImageQueued
      Observed Generation:   1
      Reason:                NotReady
      Status:                False
      Type:                  Ready
      Last Transition Time:  2025-07-16T13:45:25Z
      Message:
      Observed Generation:   1
      Reason:                ImageQueued
      Status:                False
      Type:                  ImageReady
      Last Transition Time:  2025-07-16T13:45:27Z
      Message:
      Observed Generation:   1
      Reason:                Ready
      Status:                True
      Type:                  WorkspaceReady

infrav1.IBMPowerVSImageReadyCondition here is Ready
infrav1.IBMPowerVSImageReadyV1Beta2Condition here is ImageReady condition

[Amulyam24]

why is this check needed? is it necessary to set the check for the condition on every reconcile?

[arshadd-b]

will check this

[arshadd-b]

@Amulyam24 we don't need it in this case.