Geo: Improvements and fixes after QA

We are going to move Geo (#76) to General Availability. This MR will handle all small fixes and changes to get a solid release

- [x] Replicates repository removal (using system hooks)
- [x] Replicates repository rename (using system hooks)
- [x] Replicates repository transfer (using system hooks)
- [x] Whitelisted Sidekiq routes so you can use web interface in a secondary node.
- [x] Change "Gitlab -> GitLab" for the readonly error flash
- [x] Check license add-on to allow any Geo features. 
- [x] Do not execute on a secondary node: `StuckCiBuildsWorker`
- [x] Do not execute on a secondary node: `HistoricalDataWorker`
- [x] Documentation changes: (master, slave -> primary, secondary)
- [x] Document we require `db_key_base`(secrets.yml) to be the same in all nodes

See merge request !354

Mark 8.7.0 as released



See merge request !358

[ci skip]

Refactor update documentation

Port from CE https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3822

See merge request !355

File name change appears on one line

Closes #15445

<img src="/uploads/51714555be63af16b810cf528de49192/Screen_Shot_2016-04-21_at_9.22.43_AM.png" width="500px">

See merge request !3854

Fixed issue with author link color on dark diffs

Correctly added a color to the author link

![Screen_Shot_2016-04-21_at_08.55.05](/uploads/ffa9e12e868c7b71fa4dd9244114274a/Screen_Shot_2016-04-21_at_08.55.05.png)

Fixes #15444

See merge request !3847

Use SIGTERM during Sidekiq memory shutdown

This makes the memory killer behave more like 'sidekiqctl stop'.

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/15359

Closes https://gitlab.com/gitlab-org/gitlab-ce/issues/14462

See merge request !3853

Filter labels by including ALL filter titles

Fixed query to use `AND` and not `OR`. Refactored relevant specs

See merge request !3815

This makes the memory killer behave more like 'sidekiqctl stop'.

Revert "Merge branch 'sentry-js' into 'master'"

This reverts commit 0f309794, reversing
changes made to 1e596fef.

See merge request !3851

Implement top navigation for profile area

Main idea is to keep left sidebar static so user is not confused by
changing context. Instead we put changing navigation with changing
content in one main block. I used profile area as a simplest way to 
implement and test this concept. Your feedback is welcome in comments

For https://gitlab.com/gitlab-org/gitlab-ce/issues/14354#note_4878536Signed-off-by: Dmitriy Zaporozhets <dmitriy.zaporozhets@gmail.com>

See merge request !3824

This reverts commit 0f309794, reversing
changes made to 1e596fef.

[ci skip]

Document the feature freeze starting on the 18th

cc @dzaporozhets @rspeicher @DouweM @rymai @axil 

See merge request !3698

Show project members only for members

fixes #5838 

See merge request !3752

Attempt to create pg_trgm extension in migration for test/dev environments

See merge request !3805

Fix cross-project label ref used with invalid project

When cross-project label reference was used with invalid project reference, `nil` was assigned to project variable which later caused an exception.

Closes #15168

See merge request !3811

add tap coverage example to project settings

Previously, there were examples for Simplecov, pytest-cov, and phpunit.
This adds an example for using the tap cli tool
(https://github.com/tapjs/node-tap)

Before:
![Screen_Shot_2016-04-07_at_9.57.32_AM](/uploads/2864d4cd4b5288565057263a435a851f/Screen_Shot_2016-04-07_at_9.57.32_AM.png)

After:

![Screen_Shot_2016-04-07_at_9.57.16_AM](/uploads/62901e01c4ad6db86e4ced3dfebd20b9/Screen_Shot_2016-04-07_at_9.57.16_AM.png)


See merge request !3597

Ci::Commit becomes a Pipeline object

1. Ci::Commit receives context: ref, :tag.
1. One Ci::Commit describes a one Pipeline
1. Pipeline is created from `.gitlab-ci.yml`
1. Pipeline is a ordered group of builds
1. We test MR against Pipeline
1. Pipelines have a separate view (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3703)
1. Pipeline can be triggered from UI (https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/3703)
1. Later we change `Trigger -> TriggerRequest -> Build` to `Trigger -> Pipeline` (future)
1. We add a Pipeline Hook that will be triggered on Pipeline status change  (future)
1. We extend notifications to use `Pipeline Hook` to send summary on pipeline changes (future)

After merging that I'll prepare a separate MR that will unify naming, database columns, table names:
```
Ci::Commit -> Pipeline
Ci::Build -> Build
CommitStatus -> Job
GenericCommitStatus -> ExternalJob

ci_commits -> pipelines
ci_builds -> jobs
```

This MR implements first 5 points.

This is made to solve this issue https://gitlab.com/gitlab-org/gitlab-ce/issues/14149.

See merge request !3653