Allow Inspection Of Component Request Profiles

User Story:

As a HyperShift Engineer, I want to be able to:

• measure the requests being sent by the HCCO to the management plane

so that I can achieve

• effective quota limits on our management KAS throughput

As a HyperShift Engineer, I want to be able to:

• identify the specific requests being sent by every component that talks to the management KAS by their GVR and verb

so that I can achieve

• simple and effective root-causing and debugging of KAS throughput regressions
• identification of areas to simplify and make more efficient

As a HyperShift Engineer, I want to be able to:

• measure the API load on the management KAS by component and request type (GVR, verb, etc) over axes of time, release version, hyperscaler, etc

so that I can achieve

• an understanding of trends over time, between environments, etc

Acceptance Criteria:

Description of criteria:

• HCCO exposes metrics; management Prometheus ingests them
• downscaled per-test, per-component API throughput metrics are exposed
• said metrics are visualized in a UI for ease of consumption
• said metrics can be validated by a server that can answer questions like "for this test, in this environment, on this release, is $amount of requests within reason or a regression?"

This does not require a design proposal.
This does not require a feature gate.