Upgrade to latest version the following gems:
* Spring
* Bootsnap
* Thin
* webpack-rails
* pry-rails

Implements list_last_commits_for_tree to communicate with the
ListLastCommitsForTree Gitaly RPC

Bumps the Gitaly server version

Bumps the Gitaly-Proto gem version

We remove this feature as it never worked properly

The reason for removing this gem is that it's not being maintained
anymore. It uses `alias_method_chain` which is deprecated in rails 5
(and removed in 5.1), the issue is pending upstream (including
a fix) - https://github.com/suranyami/peek-sidekiq/issues/3 for a while.

Peek-sidekiq is used in performance bar for displaying sidekiq
statistics.

See
https://github.com/ruby-grape/grape/blob/master/CHANGELOG.md#110-842018.

This fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/51299.
Signed-off-by: NRémy Coutable <remy@rymai.me>

The most significant change in this version is that the default
concurrency has been lowered from 25 to 10 (https://github.com/mperham/sidekiq/issues/3892).
This doesn't affect omnibus-gitlab because the concurrency is controlled via a
setting that defaults to 25 anyway and is passed in via the `-c` command-line
parameter.

However, source installations (including the GDK) will have to either specify
the concurrency in `sidekiq.yml` or use the `-c` option.

Full list of changes: https://github.com/mperham/sidekiq/blob/master/Changes.md

We used to apply this limitation on GitLab when using Rugged. Now that
we've shifted to Gitaly, this parameter needs to be sent via a RPC
request. Currently this value is hardcoded on Gitaly.

There were several issues:

1. With Google Cloud Storage, we can't override the Content-Type with
Response-Content-Type once it is set.  Setting the value to
`application/octet-stream` doesn't buy us anything. GCS defaults to
`application/octet-stream`, and AWS uses `binary/octet-stream`. Just remove
this `Content-Type` when we upload new files.

2. CarrierWave and fog-google need to support query parameters:
https://github.com/fog/fog-google/pull/409/files, https://github.com/carrierwaveuploader/carrierwave/pull/2332/files.
CarrierWave has been monkey-patched until an official release.

3. Workhorse also needs to remove the Content-Type header in the request
(https://gitlab.com/gitlab-org/gitlab-workhorse/blob/ef80978ff89e628c8eeb66556720e30587d3deb6/internal/objectstore/object.go#L66),
or we'll get a 403 error when uploading due to signed URLs not matching the headers.
Upgrading to Workhorse 6.1.0 for https://gitlab.com/gitlab-org/gitlab-workhorse/merge_requests/297
will make Workhorse use the headers that are used by Rails.

Closes #49957

Full list of changes: https://github.com/fnando/browser/blob/master/CHANGELOG.md

Signed-off-by: NRémy Coutable <remy@rymai.me>

This is needed to support query parameters in `Fog::Storage::Google`.
See https://github.com/fog/fog-google/pull/409.

Relates to https://gitlab.com/gitlab-org/gitlab-ce/issues/49957

See https://github.com/libgit2/libgit2/releases for more details.

Fixes failing builds with gcc on Archlinux and Ruby 2.4.4.

See https://gitlab.com/gitlab-org/prometheus-client-mmap/merge_requests/26
for more details.

As pointed out in #49625, this version is needed to support Ruby 2.5.

See https://github.com/haml/haml/blob/master/CHANGELOG.md for more details.

This will be enabled if ENABLE_RBTRACE environment variable is defined.
This will allow us to debug all sorts of issues in production:

https://github.com/tmm1/rbtrace

In 2.8.3, it was possible to modify a constant without knowing it, which
led to a major performance regression (https://gitlab.com/gitlab-org/gitlab-ce/issues/49409).
Now attempting to modify the HTML::Pipeline::SanitizationFilter.WHITELIST will result in
"can't modify frozen Hash".

See https://github.com/jch/html-pipeline/pull/299.

Without this parameter, every load of a Wiki page will load all the Wiki pages
in the repository for the sidebar. This is a significant performance penalty
that can significant slow the display of all Wiki pages.

Relates to #40101

sanitize 4.6.6 has this optimization that will benefit Markdown rendering: https://github.com/rgrove/sanitize/pull/183

nokogiri 1.4.4 has this memory leak fix: https://github.com/sparklemotion/nokogiri/pull/1771

This will enable bootsnap whenver the gem is available.