improves test settings for chat notification services for empty projects

Closes #31138

See merge request !10886

Make api/v3/deployments_spec to actually tests v3 instead of current API

See merge request !10965

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

gitter badge in the readme pointing to gitlabhq/gitlabhq

See merge request !10968

Remove invalid services with nil or empty type

See merge request !10847

Resolve "Milestone sidebar display incorect number of MR when minimized"

Closes #31292

See merge request !10933

Fix ordering of commits in the network graph.

Closes #30973

See merge request !10936

Lazily set UUID in ApplicationSetting for new installations

Closes gitlab-ee#2246

See merge request !10893

Increase code coverage for admin/cohorts page

See merge request !10964

Update mail gem to 2.6.5

See merge request !10951

Remove unused code

Closes #31202

See merge request !10897

Use vue files for vue components.

See merge request !10882

Fix checks markup in bug template

See merge request !10963

Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

Make namespace owner master of project upon creation

Closes #29446

See merge request !10910

- We upgraded `rugged` to 0.25.1.1 in !10286 for %9.1

- Prior to this upgrade, the default sort order for commits returned by
  `Gitlab::Git::Repository#find_commits` was `Rugged::SORT_DATE`, which the
  graph relied on.

- While upgrading `rugged`, the MR also changed this default to
  `Rugged::SORT_NONE`, which broke commit ordering in the graph.

- This commit adds an option to `Gitlab::Git::Repository#find_commits` to sort
  by date, and changes the graph builder `Network::Graph` so it explictly
  requests the `:date` sort order

Remove view fragment caching for project READMEs

Closes #26585 and #29594

See merge request !8838

Allow admins to sudo to blocked users

See merge request !10842

When an admin creates a project in the namespace of a user, that user
automatically gains master access to that project.

The `MarkupHelper#markup` method does everything we need here.

Because the post-processing of the rendered README is dependent on the
context (i.e. the current user), do the post-processing when the
README is being displayed.