Adds a new API endpoint that receives events from GitLab Agent (KAS).
It will track events using internal event tracking.

This removes the feature flag but keeps the new feature.

Changelog: other

Remove the `k8s_proxy_pat` feature flag. This FF has been introduced in
16.4 and the `k8s_proxy` PAT scope has been deemed stable.

Changelog: removed

Changelog: changed

Refs https://gitlab.com/gitlab-org/gitlab/-/issues/409028

Refs https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/issues/439

This refactoring prepares the endpoint for a second `access_type`, which
is the `personal_access_token` type.

See https://gitlab.com/groups/gitlab-org/-/epics/11235

This commit cleans up feature flags for Kubernetes dashboard.

Changelog: other

Refs https://gitlab.com/gitlab-org/gitlab/-/issues/366294

This MR implements the instrumentation proposal from
https://gitlab.com/gitlab-org/gitlab/-/issues/412163+
and has a corresponding implementation in KAS introduced with
https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/merge_requests/1009+.

Refs https://gitlab.com/gitlab-org/gitlab/-/issues/366294
Refs https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/merge_requests/1002

This is the rails part of
https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/issues/401+

Refs: https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/issues/401

- The initial release of the Remote Development feature guarded by a feature flag
- https://gitlab.com/gitlab-org/gitlab/-/merge_requests/105783
- See https://gitlab.com/gitlab-org/remote-development/gitlab-remote-development-docs/-/blob/main/doc/local-development-environment-setup.md

Changelog: added

Feature categories dependency_scanning and license_compliance replaced
by software_composition_analysis, according to commit
https://gitlab.com/gitlab-com/www-gitlab-com/-/commit/e1ea6909e4824563bbc176b1fd97d1c7ea977818

The type in the API was Set[Integer], but our redis HLL code doesn't
handle sets, so this was counting distinct stringified sets. Turns out
these are likely to be distinct between requests, hence the inflated
user count. We fix this by using an Array, which the redis gem handles
correctly.

See https://gitlab.com/gitlab-org/configure/general/-/issues/286

Changelog: fixed

This was an oversight, as the starboard_vulnerability endpoints do not
belong to the kubernetes_management feature_category, since it's not
developed by the Configure group.

The GitLab Agent Server (KAS) is the only component which uses this
internal API. In the current version of KAS it does not send
param[:gitops_sync_count] and params[:k8s_api_proxy_request] anymore.

We've kept these around while we were transitioning the KAS version to
change the params to use params[:counters]. It's safe to remove this
code now.

- Extends the API to also accept unique counts
- Add ci_users_using_ci_cd_tunnel event and metric
- Add track_ci_users_using_ci_cd_tunnel feature flag for this metric

Changelog: added

Changelog: added

These are internal API endpoints, called by kas only. It does not currently use the value, so it's safe to move it. It will use the value once moved. Even without the value kas works fine, so it's a safe change in any case.

This removes all `default_enabled: :yaml | true | false`

Using the has notation instead of the definition in an array makes it
easier to see where the endpoints live.

During the MR review, we've validated that some endpoints were safely
passing our 1 second default urgency. So this commit removes some global
urgency :low calls and specifies the endpoints that really need them,
leaving the rest as default 1s.

We've also refactored one of the urgency calls to include all the
necessary endpoints in the list, instead of having multiple calls to
urgency :low, [..]

Changelog: added
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/83270
Epic: https://gitlab.com/groups/gitlab-org/-/epics/7204
Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/347045

KAS queries gitaly directly for agent configuration and GitOps.
Currently, KAS mimicks this default branch logic internally, and we
suspect it may sometimes get it wrong. So this may fix a bug, but it
will also allow us to remove duplicate logic from KAS.

See https://gitlab.com/gitlab-org/cluster-integration/gitlab-agent/-/issues/210

Changelog: changed

Although this endpoint previously existed in core, it was
only ever used by EE functionality (all Agent features were
licensed).

Now that some agent features are being made available in core,
we must add license checks to any functionality that will
continue to be a paid feature.

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/68023

Changelog: added

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/60081

Changelog: added