To have better control on how `make` is ran to build Gitaly, run it from
the GitalySetup helper module.

Kernel#system by default returns false when the command fails. Before
this change the return value was not looked at. With this change we pass
`exception: true` to system() so it raises an exception on failure.

In the next commit we want to use GitalySetup.build_gitaly for local
testing. Prior to this change, HOME is set when calling `make`. But this
might break when Golang is installed through `asdf`.

This change moves setting HOME to where Gitaly is spawned only. We add a
little comment to explain this is done to make sure Git is not affected
by user configuration.

In 08af0f9f (Speed up gitaly setup in tests, 2021-07-20) the setup of
Gitaly was sped up in test by copying it over from GDK whenever
possible. This drastically reduced the setup time, but it complicates
installations of Ruby gems in Gitaly.

This change rolls back that copy-from-GDK installation, but instead
incrementally installs Gitaly. So instead of removing tmp/tests/gitaly
completely and setting up from scratch, we now fetch the revision
specified in GITALY_SERVER_VERSION and trust `make` inside the Gitaly
directory to The Right Thing(tm).

Combined with the introduction of gitlab-development-kit@d2229da0
(Makefile: Stop nuking gitlab/tmp/tests/gitaly, 2021-12-06) this should
avoid Gitaly in test ever again would be built from scratch.

In case this would not work in some situations, we look at
FORCE_GITALY_INSTALL and if the environment variable is set
tmp/tests/gitaly is deleted before installing Gitaly again.

In previous commit we started setting BUNDLE_PATH as an environment
variable, and this works great. But this value gets overridden in case
it's specified in the local config. You can see so by using the
`bundle config` command:

    $ BUNDLE_PATH=vendor/bundle bundle config path
    Settings for `path` in order of priority. The top value will be used
    Set for your local app (/home/r/gdk/gitlab/.bundle/config): "vendor/bundle"
    Set via BUNDLE_PATH: "vendor/bundle"
    Set for the current user (/home/r/.config/bundle): "vendor/bundle"

This isn't persay an issue, but in most cases this is set as a relative
path. Because different `bundle` commands might get triggered from
different directory levels in the project tree, this might become an
issue.

To overcome this, the active value of BUNDLE_PATH is read, expanded to
an absolute path and passed back to the environment. But because of the
prioritization demonstrated above, we need to set BUNDLE_IGNORE_CONFIG
so any local, user, or system configuration is ignored.

Setting up and spawning Gitaly in tests needs to have some Bundler
settings configured. Until now this was done by writing to the local
config file in the ruby directory inside the gitaly dir used in test.

This method didn't seem to be robust for all our user and
use-cases (i.e. CI), because this configuration _could_ be done from
different places.

To make the situation more predictable, this change injects all Bundler
configuration through environment variables instead.

Collect test resources and write to file

See merge request gitlab-org/gitlab!77431

Add rake task for delete test resource task
Update Resouce::Base to collect resource after creation
Add new ENV var for JSON file path
Add new tool to delete test resources
Add new tool to collect test resources
Update spec helper to write resource collection to file at end of suite

Extract agent token usage tracking logic into service

See merge request gitlab-org/gitlab!78151

Fix the order of subsequent jobs when requeuing a job

See merge request gitlab-org/gitlab!77528

Revert "Merge branch 'rajat/work-hierarchy' into 'master'"

See merge request gitlab-org/gitlab!78395

Ensure highlight.js matches the GitLab white theme

See merge request gitlab-org/gitlab!76725

Clean up VSA base template conditions

See merge request gitlab-org/gitlab!78189

Improve Gitaly test setup error message

See merge request gitlab-org/gitlab!78311

If Gitaly can't be spawned, print a more informative error explaining
possible reasons why. This commit will inform the user whether Gitaly or
Git binaries are missing.

Fix Rails/SaveBang offenses

See merge request gitlab-org/gitlab!75976

Fix Gitlab/DelegatePredicateMethods offenses

See merge request gitlab-org/gitlab!76010

Improve performance of search global service spec

See merge request gitlab-org/gitlab!78377

Remove wait_using_real_timer helper

See merge request gitlab-org/gitlab!78332

Destroy trace chunks and data when deleting pipelines

See merge request gitlab-org/gitlab!78116

This reverts commit 4f1e3e52, reversing
changes made to 78a09154.

Changelog: removed

Reintroduce adding timestamp to GitLab Standard Context

See merge request gitlab-org/gitlab!78067

Add docs for Group (SaaS) User Caps

See merge request gitlab-org/gitlab!77567

We have a standard way to write procedures,
so attempted to match that standard.
Also, added text to the titles so they'll be easier to
find via search

Blob refactor: Fix sourcegraph integration

See merge request gitlab-org/gitlab!78053

Changelog: fixed

Refactor group security discover data attributes

See merge request gitlab-org/gitlab!77781

Migrate legacy icon badge usage

See merge request gitlab-org/gitlab!78308

Update bundler to 2.3.5 because 2.1.4 is too old

See merge request gitlab-org/gitlab!78298

Enable the `GraphQL/ArgumentName` cop

See merge request gitlab-org/gitlab!76013

Expose internal_url setting for Geo secondaries

See merge request gitlab-org/gitlab!77179

Change tense of text to comply with style guidelines

See merge request gitlab-org/gitlab!77834

This reverts commit 8b49d615.

Fix GraphQL/FieldDefinitions offense (Part 3/4)

See merge request gitlab-org/gitlab!76016

Fix margin for submit button with captcha

See merge request gitlab-org/gitlab!78316

Refactor project security discover data attributes

See merge request gitlab-org/gitlab!78306

Add a workaround for 500  error on 13.9.0

See merge request gitlab-org/gitlab!78315