Enable nomaps rule for Kube API Linter

[MatteoFari]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Enable nomaps for Kubernetes API Linter with all the exceptions

Which issue(s) this PR is related to:

Part of #134671

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

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

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 @MatteoFari. Thanks for your PR.

I'm waiting for a github.com 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.

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: MatteoFari
Once this PR has been reviewed and has the lgtm label, please assign liggitt for approval. For more information see the Code Review Process.

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

Needs approval from an approver in each of these files:

• hack/OWNERS
• hack/kube-api-linter/OWNERS

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

[kannon92]

/ok-to-test
/sig architecture

[MatteoFari]

/release-note-none

[MatteoFari]

/hold

[JoelSpeed]

I wasn't expecting there to be too many violations for this linter, can we get a count per API group that you've added an exclude for please?

[JoelSpeed]

How many different violations are there in these groups?

[JoelSpeed]

To be properly scoped and effective here, we need to include the field names in the error messages. So I think lets try break this down further please, else we risk ignoring new violations in these groups

[MatteoFari]

@JoelSpeed I added the field names in the error messages so now it's better scoped. Let me know if I can go on doing the same for core and resource or should proceed in a different way.