Add custom type for resource not found error

[Amulyam24]

What this PR does / why we need it:
Add custom type for resource not found error

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:

/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 custom type for resource not found error

[netlify]

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

Name	Link
🔨 Latest commit	8ea3476
🔍 Latest deploy log	https://app.netlify.com/sites/kubernetes-sigs-cluster-api-ibmcloud/deploys/662794a83cd762000750d522
😎 Deploy Preview	https://deploy-preview-1739--kubernetes-sigs-cluster-api-ibmcloud.netlify.app
📱 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 site configuration.

[Amulyam24]

/cc @Karthik-K-N

[Prajyot-Parab]

/hold for @Karthik-K-N

[Prajyot-Parab]

/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: Amulyam24, Prajyot-Parab

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [Prajyot-Parab]

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

[Karthik-K-N]

I agree for defining these messages globally, But do we need to define them within api's, Usually api's are not only used within the repo, its meant to be imported by clients. So does these make any use for external consumption apart from using it internal? If not then we can define them within in file in scope or somewhere.

I defer the decision to you.

[Amulyam24]

I agree for defining these messages globally, But do we need to define them within api's, Usually api's are not only used within the repo, its meant to be imported by clients. So does these make any use for external consumption apart from using it internal? If not then we can define them within in file in scope or somewhere.

I defer the decision to you.

@Karthik-K-N, I agree on defining it within the package scope as it will not be used beyond it. Changes applied, PTAL!

[Karthik-K-N]

Thank you.

/lgtm

[Karthik-K-N]

/hold cancel