Map RESOURCE_OPERATION_RATE_EXCEEDED to ResourceExhausted

[amacaskill]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug

/kind cleanup

/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

What this PR does / why we need it:
Map RESOURCE_OPERATION_RATE_EXCEEDED to ResourceExhausted. Prevents us from being alerted for errors like:

CreateVolume failed to create single zonal disk pvc-xxx: failed to insert zonal disk: unknown error when polling the operation: rpc error: code = Internal desc = operation operation-xxx failed (RESOURCE_OPERATION_RATE_EXCEEDED): Operation rate exceeded for resource 'projects/xxx/global/snapshots/snapshot-pvc-xxx'. Too frequent operations from the source resource.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

Map RESOURCE_OPERATION_RATE_EXCEEDED to ResourceExhausted.

[leiyiz]

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: amacaskill, leiyiz

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 [amacaskill,leiyiz]

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

[amacaskill]

/cherry-pick release-1.15

[k8s-infra-cherrypick-robot]

@amacaskill: new pull request created: #1848

In response to this:

/cherry-pick release-1.15

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.

[amacaskill]

/cherry-pick release-1.14

[k8s-infra-cherrypick-robot]

@amacaskill: new pull request created: #1880

In response to this:

/cherry-pick release-1.14

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.