+ Add support for the new separate channel and events settings
* Dry up chat notifications in the service properties definitions

[10.2] Ensure we expose group projects using GroupProjectsFinder

See merge request gitlab/gitlabhq!2234

(cherry picked from commit 072f8f2fd6ec794645375a16ca4ddc1cbeb76d7a)

a2240338 Ensure we expose group projects using GroupProjectsFinder

Fix https://gitlab.com/gitlab-org/gitlab-ce/issues/40825

Two things at ones, as there was no clean way to seperate the commit and
give me feedback from the tests.

But the model Artifact is now JobArtifact, and the table does not have a
type anymore, but the metadata is now its own model:
Ci::JobArtifactMetadata.

To allow jobs/builds to have multiple artifacts, and to start seperating
concerns from Ci::Build a new model is created: Ci::Artifact.

Changes include the updating of the ArtifactUploader to adapt to a
slightly different interface. The uploader expects to be initialized
with a `Ci::Build`.

Futher a migration with the minimal fields, the needed foreign keys and
an index.

Last, the way this works is by prepending a module to Ci::Build so we
can basically override behaviour but if needed use `super` to get the
original behaviour.

Comments from code review applied. Also switched forked_from_project and ForkedProjectLinks to ForkNetworkMember

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

Mitigate a N+1 requests to Gitaly problem. Still one left.
Signed-off-by: NRémy Coutable <remy@rymai.me>

Closes #35794.

This returns the `real_size` of the MR's diff, which is a string indicating the
number of changes. If the diff overflows after _n_ files, the string will be
`$n+`.

Closes #35692.

This reverts merge request !14148

Revert "Merge branch '35012-navigation-add-option-to-change-navigation-color-palette' into 'master'"

This reverts merge request !13619

This finishes the procedure for migrating events from the old format
into the new format. Code no longer uses the old setup and the database
tables used during the migration process are swapped, with the old table
being dropped.

While the database migration can be reversed this will 1) take a lot of
time as data has to be coped around 2) won't restore data in the
"events.data" column as we have no way of restoring this.

Fixes https://gitlab.com/gitlab-org/gitlab-ce/issues/37241