Resolve "Add border around the repository file tree" EE

Closes gitlab-ce#50264

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

Resolve "Empty state for Packages screen"

Closes #7926

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

CE upstream - 2018-11-29 00:21 UTC

Closes gitlab-ce#38317, #8608, #2727, #2732, and #2742

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

Improve draft note header design

Closes #7920 and #7905

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

Store hashed storage paths in the database

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

Moves the pending badge into the header.
Enables the toggle resolve button to toggle the resolve status
of a draft note.

Closes https://gitlab.com/gitlab-org/gitlab-ee/issues/7905

Retry the review-qa-smoke job twice

Closes #54610

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

Fix Environment terminal specs for EE

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

Docs: add link to the docs site from /help landing page

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

Docs: add link to the docs site from /help landing page

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

Merge branch 'docs/8608-update-approval-guidelines-to-include-red-orange-data-reviews' into 'master'

Add RED data security requirement to code review

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

Remove link that is broken now

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

Commits API: Preserve file content in move operations if unspecified

Closes #52974 et #51083

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

Also, enable debug mode.
Signed-off-by: Rémy Coutable <remy@rymai.me>

Resolve conflicts for
https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8634

Resolve conflicts for https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8634

Resolve conflict in https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8634

Resolve conflicts for https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8634

And place #track_project_repository in Projects::CreateService
instead.

A shard is now the proper name for a repository storage, so Shardable
is an acceptable name for defining the repository shard.

This is a more sensible name to make clear it tracks it in the
database and not just saves it on disk.

Instead of having the foreign key `repository_id` in the `projects`
table, have a FK in the `project_repositories` table. This will:

- Reduce the size of `projects` table, which is huge already.
- Make the foreign key constraint `on_delete: :cascade` useful,
  because the `project_repositories` row will be deleted when
  `projects` row is deleted.
- Since the `project_repositories` row can only be created **after**
  the `projects` row (because hashed storage needs a `projects.id`),
  it does not require updating the `projects` row after creating the
  `project_repositories`.
- Make it easier in the future to have a N-to-M relation.

When a new project is created, or migrated to hashed storage,
create/update the project repository row.