Remove partial word matching from code search

See merge request gitlab-org/gitlab!32771

Currently the code search uses ngrams to allow searching for prefixes as
well as full matches. This takes up a lot of storage and can be replaced
with a prefix search.
This change removes the usage of edgeNGram_filter from our index
mappings.

Add example to manually delete job logs

See merge request gitlab-org/gitlab!32653

Removed a note about pagination limitations

See merge request gitlab-org/gitlab!33141

Minor refactor extract method InstrumentationHelper

Closes #219197

See merge request gitlab-org/gitlab!33133

Fix confidential note attribute getter

See merge request gitlab-org/gitlab!32571

Fix #216731 "Fetching author API under relative url"

Closes #216731

See merge request gitlab-org/gitlab!32379

This reverts commit 414bb48a2788099befa602c1454b48db02631c66.

Add Docker to capitalization rules

See merge request gitlab-org/gitlab!33134

Assign alerts sidebar base

See merge request gitlab-org/gitlab!32642

Create vale test for unresolved merge conflicts

Closes #219168

See merge request gitlab-org/gitlab!33125

This will hopefully improve readability since this method is getting a
little long now.

Check valid confidence and severity level when parsing

See merge request gitlab-org/gitlab!33050

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.