Kubernetes API reference analyzer based on types instead of field names

What does this MR do?

Switches the Kubernetes API reference generator to match on variables of a specific type instead of a certain name.

Why was this MR needed?

This makes the process less error prone as before we could miss an annotation due a field not being named a certain way. It also makes it easier to develop normal code as we don't have to think about variable names.

What's the best way to test this MR?

Tests in analyzer_test.go should pass and running mage k8s:generatePermissionsDocs should produce identical docs as before these changes.

What are the relevant issue numbers?

Closes #38304 (closed)