See https://gitlab.com/gitlab-org/gitlab-ce/issues/38261

Instead perform soft check (the column set to indicate that file does exist)

We recently started adding YAML frontmatter in docs so that we can
show more information, but that only works for the docs portal at
docs.gitlab.com.

For example, we want to add a last_updated entry
https://gitlab.com/gitlab-org/gitlab-ce/issues/37677

Whereas this is useful for the docs portal, it looks ugly for docs
under /help.

Discussions are now done asynchronously via the `IssuesController#discussions`
endpoint, so this should no longer be needed. This was taking 32% of the load
time for GitLab CE issue 1.

Closes #38034

In #37955,we see that the profile had a number of N+1 queries from repeated
access to `cross_reference_not_visible_for?`. This was optimized in previous
versions of GitLab by rendering all notes at once, counting the number of
visible references, and then using that number to check whether a system note
should be fully redacted.

There was also another N+1 query calling `ProjectTeam#member?`, which did not
take advantage of an optimization in prepare_notes_for_rendering that would
preload the maximum access level per project.

Closes #37955

Closes #37789

* Improve the descriptive text
* Rename "from" to "Target" and "to" to "Source"
* Swap "Target" and "Source" to have the same order as in MRs
* Reworded "Switch base of comparison" to "Swap versions"
Signed-off-by: NRémy Coutable <remy@rymai.me>

added a QueryRecorder for IssuesController#index.json

This reverts merge request !14148

This solves an N+1 query problem where we'd run multiple queries when
getting the namespace owners of the displayed projects.

Revert "Merge branch '35012-navigation-add-option-to-change-navigation-color-palette' into 'master'"

This reverts merge request !13619

This makes it easier to reuse in EE.

Open the settings section based on the location hash