Enable the optionalorrequired linter for the apidiscovery API group

[vinayakray19]

What type of PR is this?

/kind api-change
/kind feature

What this PR does / why we need it:

• Enable the optionalorrequired linter for the admission API group.

Which issue(s) this PR is related to:

Fixes : #136859

Special notes for your reviewer:

• This PR enables the optionalorrequired kube-api-linter rule for the apidiscovery API group as tracked in #136859

• To support this change, all fields in the apidiscovery API types have been annotated with explicit markers (+required or +optional) in accordance with Kubernetes API conventions.

• The adjustments do not alter API semantics, behavior, or compatibility; they only satisfy static analysis requirements enforced by the linter.

• The optionalorrequired rule ensures that every API field is explicitly marked as either optional or required, improving API clarity and future maintainability.

Does this PR introduce a user-facing change?

No.

NONE

[k8s-ci-robot]

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Details

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.

[k8s-ci-robot]

Hi @vinayakray19. Thanks for your PR.

I'm waiting for a kubernetes member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: vinayakray19
Once this PR has been reviewed and has the lgtm label, please assign thockin for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details

Needs approval from an approver in each of these files:

• hack/OWNERS
• hack/kube-api-linter/OWNERS
• staging/src/k8s.io/api/OWNERS

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

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