Because we do not have yet two way communication between container
registry and GitLab, we need to eagerly create a new container
repository objects in database. We now do that after user/build
successfully authenticates a push action using auth service.

Comment explains why we still have authentication without user object
there. The legacy authentication mechanism should be removed in 10.0.

This is important because method `empty?` is triggered when validation
happens, and we don't want to make API request to registry when record
is validated.

* master: (192 commits)
  Implement new service for creating user
  Update sentry-raven 2.0.2 -> 2.4.0
  Update webmock 1.21.0 -> 1.24.6
  Update spring 1.7.2 -> 2.0.1
  Update simplecov 0.12.0 -> 0.14.1
  Update pry-rails 0.3.4 -> 0.3.5
  Update pry-byebug 3.4.1 -> 3.4.2
  Update flay 2.6.1 -> 2.8.1
  Remove Tags filter from Projects Explore dropdown
  Update capybara-screenshot 1.0.11 -> 1.0.14
  Update bullet 5.2.0 -> 5.5.1
  Update brakeman 3.4.1 -> 3.6.1
  Remove web-console gem
  Update better_errors 1.0.1 -> 2.1.1
  Display flash message to unauthenticated user when creating new issue
  Fix up emoji tests that should have failed :/
  Fix RSpec/DescribeSymbol cop violations
  Add event limit warning all tabs Cycle Analytics
  Adding non_archived scope for counting projects
  Resolve "Gitlab administrator cannot create projects in every group"
  ...

Conflicts:
	db/schema.rb

Resolve "Add event limit warning to all Cycle Analytics tabs"

Closes #29935

See merge request !10179

Merge branch '20204-new-issue-button-redirects-you-to-create-a-new-issue-after-logging-in' into 'master'

Resolve "New issue button redirects you to create a new issue after logging in"

Closes #20204

See merge request !10153

Remove Tags filter from Projects Explore dropdown

Closes #28992

See merge request !10242

Implement new service for creating user

Closes #27878

See merge request !9220

Gem updates

See merge request !10237

Fix RSpec/DescribeSymbol cop violations

See merge request !10229

Fix projects_limit RangeError on user create

Closes #29116

See merge request !10209

Problems:

1. It's huge.
2. It's loaded on page load, which makes the page take 13 seconds.
3. It has a terrible UX.

Closes #28992