refactor(status): make route types generic

[the-wondersmith]

Subject

Prepare to expand linkerd's repertoire of supported Gateway API route types in linkerd-policy-controller-k8s-status.

Problem

Currently, the policy controller's status component is written with HTTPRoute support (effectively) exclusively, both in its structure/organization as well as its naming (e.g. HttpRoute as a primary type name, update_http_route as a method name, etc...).

In order to expand linkerd's support for the route types defined by the Gateway API, the policy controller's status component needs to be made more generic in both respects.

Solution

NOTE: PR was opened out of order and should only be merged after #12662

PR introduces structural and naming changes making the codebase generic with respect to the type of route being handled (e.g. HTTPRoute -> Route). Changes are almost entirely cosmetic introducing only a couple of minor functional changes, most notably:

• making the status argument to make_patch generic
• adding a type-aware api_version helper method to NamespaceGroupKindName
  • note: required for proper handling of different route types in the future

Validation

• maintainer review
• tests pass

Fixes Lays Groundwork For Addressing

• policy: Support Gateway API GRPCRoute resources #12404