Adopt kube-api-linter and fix findings

[lentzi90]

/kind feature

KAL is a static analysis linter for Kubernetes API types. It enforces best practices from the Kubernetes API Conventions, catching mechanical API review issues so human reviewers can focus on higher-level design.

Upstream CAPI has already adopted KAL (tracked in kubernetes-sigs/cluster-api#11834) and it would make sense for us to follow suit. Adopting KAL during the v1beta2 API work would be ideal.

I think we can split this up into at least three PRs:

1. Add KAL to the repo, but ignore any issues it finds
2. Fix all issues that can be automatically fixed by KAL
3. Manual changes, possibly over multiple PRs depending on findings