This only changes behaviour for masters, as developers are already prevented from updating/deleting tags without the Protected Tags feature

Fixes ProtectedBranches#create flash errors bug due to
typo in 'flash[:alert] = @protected_branches.errors'

This memorized array appears to originally come from https://gitlab.com/gitlab-org/gitlab-ee/commit/19c2c90ccac86a21eb4266b9a5972162f917f692 which has a commit message of ‘fix warnings’. Without any comments on the original pull request I think we can safely get rid of it unless warnings re-appear.

Makes it clear this is only used in dropdowns, instead of cluttering up Project class. Since we only care about branch names, it is also possible to refactor out a lot of the set/reject logic.

A benchmark on Array/Set subtraction favoured using Arrays. This was with 5000 ‘branches’ and 2000 ‘protections’ to ensure a similar comparison to the commit which introduced using Set for intersection.

Comparison:
   array subtraction:      485.8 i/s
     set subtraction:      128.7 i/s - 3.78x slower

ProtectedTagEdit class for edit protected tags

Protected Tags List initializer

Export Protected Tags Editing classes

Initialize Protected Tags Edit functionality

Render Push levels dropdown

Increase dropdown width within Tags list

Update column widths

Uncommented protected tags feature specs copied from protected branches

Should provide basic CRUD backend for frontend to work from. Doesn’t include frontend, API, or the internal API used from gitlab-shell

Added schema.rb for protected tags
Removed unnecessary table ‘protected_tag_merge_access_levels’
Fixed timestamps on protected_tags

Protect tag partial
Apply styles to protected tag same as protected branch
Render protected tags within Project Settings > Repository
Protected Tags Classes
Re-export protected tag classes
Initialize Protected tags feature under Repository Settings page
Update property names for tags
Add protected tags to bundle config

Fix sticking of the database load balancer

See merge request !1502

CE upstream: Tuesday

Closes gitaly#166 and gitaly#168

See merge request !1565

Port of 28732-expandable-folders to EE

See merge request !1538

Allow to edit build minutes per user ee

Closes gitlab-ce#30163

See merge request !1535

remove useless queries with false conditions (e.g 1=0)

Closes #29492

See merge request !10141

CE Upstream - Monday

Closes gitaly#148

See merge request !1560

Don't autofill kubernetes namespace

See merge request !10438

Backport differences in global search from EE to CE

See merge request !10445

Improves Jira integration documentation

Closes #29670

See merge request !10067

Add long polling diagrams

See merge request !10270

Update patch_versions.md, add `yarn:install` in `Clean up assets and cache` command.

See merge request !10442

Remove index for users.current sign in at

Closes #29523

See merge request !10401

Split status and confidentiality action

See merge request !10443

Fix elasticsearch global code search following https://gitlab.com/gitlab-org/gitlab-ce/merge_requests/9655

There were 3 problems with sticking:

1. When sticking to a request (based on a previous request) we would
   always overwrite the WAL pointer, leading to a user being stuck to
   the primary for too long.

2. Sticking was not working for the Grape API. The API in particular is
   tricky because we have to stick either using a user, CI runner, or a
   CI build.

3. Refreshing of permissions did not lead to the refreshed users being
   stuck to the primary. This could result in users not being able to
   access new resources for a brief moment of time, or them still being
   able to see old resources.

To solve this some of the Grape related logic is handled by injecting EE
specific modules in the right places. This ensures we can stick as early
as possible, using the right data. The same technique is applied for
various parts of the CI codebase.

Backport API changes needed to fix sticking in EE

See merge request !10376