Add subresource status for vpa

[wu0407]

Add status field in subresource on crd yaml and add new ClusterRole system:vpa-actor to patch /status subresource.
The metadata.generation only increase on vpa spec update.
Fix e2e test for patch and create vpa

What type of PR is this?

/kind bug
/kind failing-test
/kind api-change

What this PR does / why we need it:

Current vpa crd has empty subresource field, that leads to metadata.generation increase on vpa status update.
The controller-runtime has GenerationChangedPredicate to filter out update status event for cr, but it not work for vpa.
This PR add status field in subresource on crd yaml and add new ClusterRole system:vpa-actor to patch /status subresource.
The metadata.generation only increase on vpa spec update.

Which issue(s) this PR fixes:

Fixes #5675

Special notes for your reviewer:

Previous pull request is #5680 #5766 and be revert #5738 #5897, because of e2e test failed #5727.

This PR compare with previous PR #5766, only add subresources in v1beta2.
https://github.com/kubernetes/autoscaler/compare/master...wu0407:autoscaler:add-status-subresource?expand=1#diff-b2539c9dfcc061e38b1961b5e52a8aed413750d74b71c018a3f6ca7dfc871efaR752-R753
@kwiesmueller @jbartosik

Does this PR introduce a user-facing change?

Added the /status subresource to VPA
action required: If you're installing VPA with different means than the `hack/vpa-up.sh` script, you need to add the ClusterRole `system:vpa-status-actor` and corresponding ClusterRoleBinding yourself. Otherwise VPA will no longer be able to update the recommendations!
If you create vpa with status,  status be ignored in apiserver, so need to update status after create vpa.

Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:

[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.

[voelzmo]

/lgtm

[jbartosik]

I don't see any problems but previous 2 times we didn't spot problems in review either.

I'd rather not roll back this for the 3rd time. I think we should run e2e tests before merginig.

[kwiesmueller]

/hold
I'll run e2e tests.

[kwiesmueller]

@wu0407 I'm rebasing onto upstream/master to get some changes needed to run e2e tests needed.
Please do the same to this PR just to be sure I'm testing the same changes as we have here.

[kwiesmueller]

./hack/run-e2e-tests.sh full-vpa passed

[kwiesmueller]

/hold cancel
/lgtm

[wu0407]

@wu0407 I'm rebasing onto upstream/master to get some changes needed to run e2e tests needed. Please do the same to this PR just to be sure I'm testing the same changes as we have here.

rebase done

[jbartosik]

/lgtm
/approve
🤞

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jbartosik, wu0407

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:

• vertical-pod-autoscaler/OWNERS [jbartosik]

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