[master] Validate bundle files before unpacking them

Closes #2770

See merge request gitlab/gitlabhq!2772

Refactor checking personal project limits

See merge request gitlab-org/gitlab-ce!24396

Enable FactoriesInMigration cop for background migrations

See merge request gitlab-org/gitlab-ce!24425

Enable FactoriesInMigration cop for background migration specs

See merge request gitlab-org/gitlab-ee!9183

Refactor Project#after_create_default_branch

See merge request gitlab-org/gitlab-ce!24329

Update changelog entry for !18425

See merge request gitlab-org/gitlab-ce!24432

See https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/18425

Add badge count to projects

Closes #29798

See merge request gitlab-org/gitlab-ce!18425

Extract process_name from GitLab::Sentry

See merge request gitlab-org/gitlab-ce!24422

Document graphicsmagick installation for source installation

Closes #56322

See merge request gitlab-org/gitlab-ce!24404

GitLab::Sentry has a program_context method to determine whether a
Sentry exception occurred in Sidekiq or rails. Since we will need
similar functionality for distributed tracing, this change extracts the
program_context method into GitLab.process_name for more general
consumption.

This refactors some of the logic used for protecting default branches,
in particular Project#after_create_default_branch. The logic for this
method is moved into a separate service class. Ideally we'd get rid of
Project#after_create_default_branch entirely, but unfortunately
Project#after_import depends on it. This means it has to stick around
until we also refactor Project#after_import.

For branch protection levels we introduce
Gitlab::Access::BranchProtection, which provides a small wrapper around
Integer based branch protection levels. Using this class removes the
need for having to constantly refer to Gitlab::Access::PROTECTION_*
constants.

Resolve "In Merge Request diff screen, master is not a hyperlink"

Closes #52275

See merge request gitlab-org/gitlab-ce!23874

This refactors the code used for checking if a user has exceeded the
personal projects limit. As part of this refactor the method has been
renamed from Project#check_limit to "check_personal_projects_limit", as
this name makes it much more clear what the purpose of the method is.
Standalone unit tests have also been added, as before we only had a
single generic validation test that did not cover all cases.

The old implementation of the refactored method also included a `rescue`
statement. This code would only run when a project creator was not set.
The error that would be added wasn't super useful, especially since
there would already be errors for the creator not being present. As none
of the other code in the "check_personal_projects_limit" raises, it has
been removed.

Removes not needed props in FF

See merge request gitlab-org/gitlab-ee!9181

Removes console.log

See merge request gitlab-org/gitlab-ee!9172

Enable Gitlab-Pages for subgroups

See merge request gitlab-org/gitlab-ce!23505

Now we're correctly rendering 404 page

Closes #9234

See merge request gitlab-org/gitlab-ee!9184

The Background migration specs also run against a certain version of
the database. So we should avoid using factories.

Fix RSpec/FactoriesInMigrationSpecs in two files

See merge request gitlab-org/gitlab-ce!24405

Add group ful path to project's shared_with_groups

See merge request gitlab-org/gitlab-ce!24052

Deletes forgotten console.log in specs

chore(rubocop): fix Style/TrivialAccessors issues

See merge request gitlab-org/gitlab-ce!24416