Assert against expected unique user counter api
What does this MR do and why?
This MR ensures that assertions for these unique-by-user internal events include the user
in the method call:
- k8s_api_proxy_requests_unique_users_via_ci_access
- k8s_api_proxy_requests_unique_users_via_pat_access
- k8s_api_proxy_requests_unique_users_via_user_access
This impacts only specs, so service ping still correct.
MR acceptance checklist
Please evaluate this MR against the MR acceptance checklist. It helps you analyze changes to reduce risks in quality, performance, reliability, security, and maintainability.
Related to #439982 (closed)