Always sort Elasticsearch searches by relevance not updated_at

See merge request gitlab-org/gitlab!36774

Updating integrations overview documentation

See merge request gitlab-org/gitlab!36496

Add front matter and fixes to some topics

See merge request gitlab-org/gitlab!37044

Docs: Removed Runner content

See merge request gitlab-org/gitlab!37119

Doc: Update metadata group label

See merge request gitlab-org/gitlab!37140

Update kubernetes.rb to read entire file

See merge request gitlab-org/gitlab!31254

- writing all intermediate ca certificates to a file and passing file path for kubernetes connection

Sidebar add to-do for alert (Alert todo create mutation)

See merge request gitlab-org/gitlab!34175

Hook up todo mutation to button

Update Terraform code example on index.md

See merge request gitlab-org/gitlab!36677

Send an email when MR is set to MWPS

See merge request gitlab-org/gitlab!33460

Add API support for instance clusters

Closes #31000

See merge request gitlab-org/gitlab!36001

Remove obsolete code in importers and remove new_import_ui feature flag"

See merge request gitlab-org/gitlab!35748

Paginate the notes incremental fetch endpoint

See merge request gitlab-org/gitlab!34628

Returning an unlimited number of elements from any endpoint is a bad
idea. For the notes endpoint specifically, we return all notes since
a given `X-Last-Fetched-At` value. The backend specifies the new value
to use for that item in the response, so if we return a limited set of
notes and use an appropriate value, we get a rudimentary form of keyset
pagination for free.

The way the notes endpoint is used today, this is mostly a theoretical
worry, and in practice, basically every response will fit within a
single page anyway. However, we can use the `notes` endpoint *instead
of* the `discussions` endpoint to fill a merge request discussion from
the beginning of time. When we do this, large discussions are loaded in
batches automatically, using pre-existing frontend code. So this change
is best seen as preparatory work for removing `discussions` altogether.

This commit also fixes a pre-existing problem with the endpoint, which
is the fact that `updated_at` is stored with *microsecond* precision in
the database. Converting the X-Last-Fetched-At value from integer to
float allows us to avoid a range of boundary conditions that result.

Merge tslint with eslint

See merge request gitlab-org/gitlab!36400

**TL;DR** Elasticsearch defaults to sorting by `_score` and this is what
we want so remove all the explicit sorting.

At present some searches are being sorted by `_score` (ie. the relevance
score) while others are being first sorted by `updated_at` then
`_score`.

There doesn't really appear to be any good reason to use `updated_at` as
the primary sort followed by `_score` since this will bury the most
relevant matches behind lots of recent matches. Using sort in this way
will only ever sort by `_score` if the `updated_at` was equal but this
is basically never going to happen since these are timestamps so
`_score` in practice is never factoring in to the sorting which probably
was never the intent here.

Since the [default sorting is by
score](https://www.elastic.co/guide/en/elasticsearch/guide/master/sorting.html)
we can leave it out of all queries.

We can in future look into whether or not we want recency to factor into
the sorting using more advanced tools like
[`function_score`](https://www.elastic.co/guide/en/elasticsearch/guide/current/function-score-query.html)
but for now sorting just by relevance is better than sorting just by
`updated_at`.

Remove GitlabIssueTrackerService records

See merge request gitlab-org/gitlab!35221

The GitlabIssueTrackerService class is not used anymore
and will be removed too.

Exposing GitLab managed apps logs - Documentation Update

See merge request gitlab-org/gitlab!37096

Product Analytics collector

See merge request gitlab-org/gitlab!36443

Rack application within Rails to record product analytics events.
Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Why:

* https://gitlab.com/gitlab-org/gitlab/-/issues/36059

This change addresses the need by:

* Remove references to TSLint.
* Update TypeScript references to point to the ESLint analyzer.
* Remove tslint-sast job from the SAST.gitlab-ci.yml file.
* Update eslint-sast job in the SAST.gitlab-ci.yml file to be triggered
  by TypeScript files.

Side effects:

* TypeScript vulnerabilities may be auto closed and reopened by the
  ESLint analyzer.

Present only issues visible to user in Vulnerabilitiy Issue Links API

See merge request gitlab-org/gitlab!36987

Verbiage tweaks for SAST config MRs

See merge request gitlab-org/gitlab!36831

Add state events to API

See merge request gitlab-org/gitlab!35210

add a commonly used virtualenv directory as a sample path to exclude

See merge request gitlab-org/gitlab!37124

include gl-coverage-fuzzing-report.json in artifacts

See merge request gitlab-org/gitlab!37110

Add a version number to metrics dashboard cache keys

See merge request gitlab-org/gitlab!37081

Swap Grape over to Gitlab::Json

See merge request gitlab-org/gitlab!36472

Forces Grape to use `Gitlab::Json` for rendering JSON,
rather than going through ActiveSupport or its own wrapper.

Updated docs to reflect current capabilities

See merge request gitlab-org/gitlab!37085

Add securing page to clusters documentation

Closes #222740

See merge request gitlab-org/gitlab!36875

Add documentation for PagerDuty incident integration

Closes #227211

See merge request gitlab-org/gitlab!37069