This will allow us to get a detailed break down of time spent in
Elasticsearch requests by controller and action. This is following the
same pattern used in `lib/gitlab/metrics/redis_rack_middleware.rb`.

Introduce instrumentation for all Elasticsearch HTTP requests

Closes #214279

See merge request gitlab-org/gitlab!32822

Remove update  function logic from List model

See merge request gitlab-org/gitlab!31900

Remove moveIssue logic from  list model

See merge request gitlab-org/gitlab!32242

Remove findLabel logic from issue model

See merge request gitlab-org/gitlab!32239

Remove temporary datepicker position fix as it is no longer required

See merge request gitlab-org/gitlab!31836

Externally installed helm dependency

See merge request gitlab-org/gitlab!32935

Add context menu links to metrics dashboard panel

Closes #215497

See merge request gitlab-org/gitlab!32646

This change allows the user to define "links" in their panel definition
to see them displayed next to their chart as a quick action to visit
other pages.

Alert table mobile hotfix

See merge request gitlab-org/gitlab!33047

Remove removeissue logic to from list model

See merge request gitlab-org/gitlab!32249

Remove findIssue logic from list model

See merge request gitlab-org/gitlab!32241

Remove newIssue function logic from list model

See merge request gitlab-org/gitlab!32244

Remove addAssignees logic from issues model

See merge request gitlab-org/gitlab!32231

Remove LSIF API endpoints which aren't used

See merge request gitlab-org/gitlab!32325

Add Kubernetes::NetworkPolicy#autodevops?

See merge request gitlab-org/gitlab!32715

This introduces the same pattern of instrumentation [we use for
Redis](https://gitlab.com/gitlab-org/gitlab/-/blob/b16db2726d7b429d740ef3642dda13b528fc4fda/lib/gitlab/instrumentation/redis.rb).
This MR also adds the instrumentation details to sidekiq logs like we do
with Redis.

This instruments at the lowest level by instrumenting the
elasticsearch-transport gem which is used by the elasticsearch-rails gem
and elasticsearch-api gem which are the higher level abstractions used
by GitLab. This has been tested to log requests coming from both places.

Other options considered for this solution involved following a similar
pattern to
https://github.com/elastic/elasticsearch-rails/blob/1c3226d8186af6e8446fa5091f5b27760c29f896/elasticsearch-rails/lib/elasticsearch/rails/instrumentation/log_subscriber.rb
which would extend the log subscriber pattern to be more than just
searches in the context of the elasticsearch-rails gem but this seemed
more convoluted than the approach I took since it requires monkey
patching to publish a message then a separate class to subscribe and
store those messages and so the pattern didn't seem to be beneficial
unless you plan to have multiple subscribers.

Additionally I considered using Faraday middleware to track this since
the Elasticsearch gem uses Faraday by default but again I opted not to
do that since it seemed trickier to manipulate the client config
following
https://github.com/elastic/elasticsearch-ruby/tree/master/elasticsearch-transport#transport-implementations
and implement the required middleware etc. than just prepending the
method following the same pattern as Redis.

Create operations_feature_flags_issues Table

See merge request gitlab-org/gitlab!32876

For linking feature flags and issues

Fix Merge Request Note Label URLs

See merge request gitlab-org/gitlab!30428

Standardize template names

See merge request gitlab-org/gitlab!32612

Infer merge request in Discussions::ResolveService

See merge request gitlab-org/gitlab!32932

Docs - how to get license details via Rails console

See merge request gitlab-org/gitlab!33123

Merge branch '219193-foss-job-failure-with-unintialized-constant-uninitialized-constant-gitlab-throttle-in-spec' into 'master'

Remove `/config/initializers/rack_attack.rb` from `.gitignore`

Closes #219193

See merge request gitlab-org/gitlab!33128

We used them for the first code intelligence iteration
Now we don't need them, so we can remove

Add docs for the PostHog cluster application

See merge request gitlab-org/gitlab!29152

This change allows Discussions::ResolveService to infer the related
Merge Request without the params[:merge_request] being present.

Previously the param was expected to be passed and the service would
error if it were not present.

This change is being made for two reasons:

1) Discussions can be associated with Designs, which have no
relationship with Merge Requests. In order to be able to use this
service to resolve Discussions on Designs, we need to make this service
able to treat the param as optional.

2) This service is to be called from within the GraphQL API. It
shouldn't be the API's responsibility to find the related Merge Request
and pass it to the service, but instead the service should be
responsible for making sure the right services are called after
resolving Discussions on Merge Requests.

The params[:merge_request] has been kept as an optimisation for existing
code that has fetched the Merge Request already before calling the
service (this won't be the case for the GraphQL API).

https://gitlab.com/gitlab-org/gitlab/-/issues/13049

Added AWS credentials for Docker credential helper

See merge request gitlab-org/gitlab!30938

Docs: Add no transfer note

See merge request gitlab-org/gitlab!33086