Make documentation linter show target path

See merge request gitlab-org/gitlab!18895

- We are seeing flaky documentation lint checks that do not always catch
  when a file inside the documentation is set with the executable bit.
  The check to find executable documents runs inside a subshell and its
  error output is not being redirected, nor would it count those errors
  when running `wc -l`. It seems implausible that we are failing to `cd`
  into the correct directory, but this is the one method I know of that
  would cause the `find` expression to fail silently in the logs. It is
  also just useful to see that yes, we are running the documentation
  linter against a reasonable directory in the logs.

Related https://gitlab.com/gitlab-org/gitlab/issues/28010Signed-off-by: Robert Marshall <rmarshall@gitlab.com>

Re-raise exception if there is no response

Closes #34332

See merge request gitlab-org/gitlab!18856

It's possible that `rescue ExceptionWithResponse` could catch a
type of exception that has no response. So we need to check if there
is a response before we return it

Allow Gitaly to work without a PG connection

Closes #34205

See merge request gitlab-org/gitlab!18659

Gitaly didn't require a PG connection to connect to, though recently we
started to pass feature flags to Gitaly in different manners. That
change would now require a PG to be running. This is not ideal,
especially if only for feature flags.

This change rescues a bad connection error, and breaks the required
dependency between PG and Gitaly.

Closes https://gitlab.com/gitlab-org/gitlab/issues/34205

Add more information for pre and post

See merge request gitlab-org/gitlab!18773

Use long_timeout for fetch_internal_remote GRPC

See merge request gitlab-org/gitlab!18908

Enable frozen string for spec/migrations

See merge request gitlab-org/gitlab!18858

Partially addresses:

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

Fix confusion in background verification doc

See merge request gitlab-org/gitlab!18836

This call is currently only used by `UpdateRepositoryStorageService`,
and it can easily time out after 30 seconds for large projects. Increase
it to a long timeout to ensure this doesn't fail prematurely.

Encountered in
https://gitlab.com/gitlab-com/gl-infra/production/issues/1250

Fix bad image permissions

See merge request gitlab-org/gitlab!18910

Images shouldn't have the +x bit

Time limit database lock when rebasing a merge request

See merge request gitlab-org/gitlab!18481

Expose prometheus status to monitor dashboard

See merge request gitlab-org/gitlab!18289

Add tests for presence and absence of cluster and deployment platform

Update Global Policy to Reject Anonymous Users For read_operations_dashboard

See merge request gitlab-org/gitlab!18687

Adjust global policy

Zoom meetings model and migrations

See merge request gitlab-org/gitlab!17890

Add Active Record backed class `ZoomMeeting`s to persist and validate
zoom links associated to an issue. We also associate meetings to a
project (via project_id) to avoid table joins. `ZoomMeeting`s can have
an issue_status of `added` or `removed` which will be used to show or
hide the zoom link on an issue via quick actions.

Removes an exception that prevented stable CI builds

See merge request gitlab-org/gitlab!18906

* This prevents CI from constructing a pipeline for stable branches,
let's fix that situation

Create loop_runner module to run test repeatedly

See merge request gitlab-org/gitlab!18546

Create QA::Specs::LoopRunner
Call LoopRunner with --loop CLI option
Allow loop duration to be set with an ENV var

Remove self monitoring project alerting token migration

See merge request gitlab-org/gitlab!17049

- Remove it since it will not do anything since the migration that adds
the self-monitoring project itself has been removed.
- The migration does not fail since it checks for the existence of the
self-monitoring project.

Add spec for filtering by multiple types

See merge request gitlab-org/gitlab!18489

Disallow running untagged jobs by default in tests

Closes #34356

See merge request gitlab-org/gitlab!18850

Fix incorrect selection of custom templates

Closes #9146

See merge request gitlab-org/gitlab!17205

Scope feature flag `job_log_json` to project

See merge request gitlab-org/gitlab!18883

Refactor stage_spec to Jest

Closes #31625

See merge request gitlab-org/gitlab!16854

* Switches to Jest for stage_spec
* Uses snapshots to simplify test code

`MergeRequest#rebase_async` can lock indefinitely with a SELECT FOR
UPDATE call. If an update is idle in transaction or another rebase
attempts to run, `MergeRequest#rebase_async` could queue indefinitely or
until statement timeouts are triggered.

To limit the impact of this operation, we now just bail out after 5 s if
we can't get the lock. The user will see an error message if this
happens.

Part of https://gitlab.com/gitlab-org/gitlab/issues/30528

Fix typo in generic alerts integration documentation

See merge request gitlab-org/gitlab!18889

Previously if multiple project templates had similar names, it was
possible the wrong template were used. For example, if you had three
different templates with the names:

1. docker
2. docker-image
3. docker-image-and-app

Clicking on `docker` would cause the search to match all three items,
and `CreateFromTemplateService` would just pick the first one returned
from the database.

Instead of using names, this commit uses the project ID to avoid this
ambiguity.

The backend support for this feature went in GitLab 12.4 via
https://gitlab.com/gitlab-org/gitlab/merge_requests/18178. This change
updates the frontend to use this.

Closes https://gitlab.com/gitlab-org/gitlab/issues/9146