Promote apiserver.config.k8s.io/v1, kind=AdmissionConfiguration

[liggitt]

What type of PR is this?
/kind cleanup

What this PR does / why we need it:

• This promotes apiserver.config.k8s.io/v1alpha1, kind=AdmissionConfiguration to apiserver.config.k8s.io/v1, kind=AdmissionConfiguration with no schema changes. This was added in v1.6.0 and has been in use with no changes since then.
• Docs update in Update docs for AdmissionConfiguration v1 website#17548

There are efforts in progress to graduate individual admission configurations (like resourcequota), and those require plumbing information through this config type.

Does this PR introduce a user-facing change?:

kube-apiserver: The `AdmissionConfiguration` type accepted by `--admission-control-config-file` has been promoted to `apiserver.config.k8s.io/v1` with no schema changes.

/sig api-machinery
/cc @deads2k @derekwaynecarr
fyi @ahg-g @ravisantoshgudimetla

[fejta-bot]

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: liggitt

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:

• hack/OWNERS [liggitt]
• staging/src/k8s.io/apiserver/OWNERS [liggitt]
• staging/src/k8s.io/apiserver/pkg/apis/OWNERS [liggitt]
• vendor/OWNERS [liggitt]

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

[liggitt]

/priority important-soon

related to #76310

[liggitt]

/retest

[ravisantoshgudimetla]

/lgtm

/hold

for @deads2k to review

[deads2k]

/hold cancel

[ahg-g]

/retest

[liggitt]

the pull-kubernetes-node-e2e-containerd failure is known, not a flake, non-blocking, and being worked on - #85040

[ahg-g]

the pull-kubernetes-node-e2e-containerd failure is known, not a flake, non-blocking, and being worked on - #85040

This was failing since yesterday, more than few PRs get merged since this started to fail, retesting few times actually works.

/test pull-kubernetes-node-e2e-containerd

[k8s-ci-robot]

@liggitt: The following test failed, say /retest to rerun them all:

Test name	Commit	Details	Rerun command
pull-kubernetes-node-e2e-containerd	1234290	link	/test pull-kubernetes-node-e2e-containerd

Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR.

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/test-infra repository. I understand the commands that are listed here.