Regenerate ProvisioningRequest CRD for v1

[aleksandra-malinowska]

What type of PR is this?

/kind bug
/kind api-change

What this PR does / why we need it:

In #7195 ProvisioningRequest API was bumped to v1, but CRD wasn't upgraded. CA 1.31 won't work without upgraded CRD.

Special notes for your reviewer:

Does this PR introduce a user-facing change?

Adds CRD for ProvisioningRequest v1

/cc @MaciekPytel @mwielgus

[k8s-triage-robot]

This PR may require API review.

If so, when the changes are ready, complete the pre-review checklist and request an API review.

Status of requested reviews is tracked in the API Review project.

[aleksandra-malinowska]

For future reference: the same go module workarounds as in #7195 were necessary, I just didn't keep the commits this time since this is already explained in the previous PR.

[mwielgus]

/lgtm

[mwielgus]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aleksandra-malinowska, mwielgus

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:

• cluster-autoscaler/OWNERS [aleksandra-malinowska,mwielgus]

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

[aleksandra-malinowska]

/cherry-pick cluster-autoscaler-release-1.31

[k8s-infra-cherrypick-robot]

@aleksandra-malinowska: new pull request created: #7316

In response to this:

/cherry-pick cluster-autoscaler-release-1.31

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.