Integrate time tracking frontend and backend

Closes #985 

See merge request !870

Rely on Gitlab::Shell public API, not reading internal files it may use

EE brother of gitlab-org/gitlab-ce!7557 so that specs can pass on EE until the CE->EE merge (no need to pick it into stable since the CE MR will be picked already).

See merge request !887

This was breaking the spec spec/features/merge_requests/created_from_fork_spec.rb
which was trying to visit a MergeRequest after the source project was
deleted.

Rely on Gitlab::Shell public API, not reading internal files it may use

EE brother of gitlab-org/gitlab-ce!7557 so that specs can pass on EE until the CE->EE merge (no need to pick it into stable since the CE MR will be picked already).

See merge request !887

[CE] Remove race condition while deleting groups

- EE version of gitlab-org/gitlab-ce!7528
- Related to gitlab-org/gitlab-ce#23223

See merge request !886

Added Backfill service for Geo

Geo nodes now can be synced without rsync. The sync will be triggered using our own transport method instead
and it will be triggered from the primary node at the moment a secondary node is created.

![](https://gitlab.com/gitlab-org/gitlab-ee/uploads/5a0eae3c9bf6620121e171bc07ca0a61/GeoNode_backfill.png)

Fixes #1190

cc @brodock @regisF

See merge request !861

It ensures we rely on `Gitlab::Shell`'s public API and not on its
internal. Since `Gitlab::Shell` is caching the value of its token, the
only way to get the correct token is to call
`Gitlab::Shell.secret_token`, not to read the
`Gitlab.config.gitlab_shell.secret_file` file!
Signed-off-by: Rémy Coutable <remy@rymai.me>

- Use multiple threads / database connections to:

  1. Escape the transaction the spec seems to be running
     in (`config.use_transactional_fixtures` is off, but
     `ActiveRecord::Base.connection.open_transactions` is not empty
     at the beginning of the spec.

  2. Simulate a Sidekiq worker performing the hard delete outside of the
     soft-delete transaction.

- The spec is a little clunky, but it was the smallest thing I could get
  working - and even this took a couple of hours. Let me know if you
  have any suggestions to improve it!

The intended flow is:

  Soft-delete group (sync) -> Delete group projects (async) -> Hard-delete group (async)

The soft-delete was run in a transaction, which was committed only after
the async job (for hard-deletion) was kicked off. There was a race
condition here - the soft-delete transaction could complete _after_ the
hard delete completed, leaving a soft-deleted record in the database.

This commit removes this race condition. There is no need to run the
soft-delete in a transaction. The soft-delete completes before the async
job is kicked off.

The database should not have any soft-deleted groups. Due to a race
condition (soft-delete completes after the hard-delete), soft-deleted
groups were (incorrectly) left in the database, causing issues while
trying to create a new group with the same name.

CE upstream

See merge request !880

Conflicts:
	app/helpers/issuables_helper.rb

This was causing things to explode with having 2 versions of Vue on the page at the same. Webpack will save us once we get that merged in

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