[cluster-autoscaler-1.34] Add peer fields to replace inlined Kubernetes API fields

[jackfrancis]

What type of PR is this?

/kind api-change

What this PR does / why we need it:

This is a manual cherry-pick of #8660.

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?

NONE

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

[jackfrancis]

/test pull-cluster-autoscaler-e2e-azure-1.34

[k8s-ci-robot]

@jackfrancis: The specified target(s) for /test were not found.
The following commands are available to trigger required jobs:

/test pull-autoscaling-e2e-vpa-full

The following commands are available to trigger optional jobs:

/test pull-autoscaling-e2e-ca-build

/test pull-cluster-autoscaler-e2e-azure-1-34

Use /test all to run the following jobs that were automatically triggered:

pull-autoscaling-e2e-ca-build

In response to this:

/test pull-cluster-autoscaler-e2e-azure-1.34

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.

[jackfrancis]

@liggitt when this lands in the 1.34 branch we can do this:

Yes. That means we should cut a patch release with this change now to seed use of the new peer fields and encourage integrations to update and start making use of the new wrapper / proto / peer fields now so they can straddle 1.34/1.35 without disruption.

cc @towca

[jackfrancis]

/test pull-cluster-autoscaler-e2e-azure-1-34

[jackfrancis]

/assign @towca

[jackfrancis]

@towca reminder that we need to land this in 1.34 branch (and cut a patch release) before we prep for the breaking change that will be introduced in 1.35

[towca]

Sorry for missing this, LGTM!

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jackfrancis, towca

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 [jackfrancis,towca]
• hack/OWNERS [jackfrancis,towca]

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