There were a number of issues with this spec:

1. The deletion of the U2F device needed an `accept_confirm` block
2. The "We heard back from your U2F device" message is shown only briefly
   before the JavaScript handler submits the form. The only way to fix this is
   to put a delay in the submission.
3. The "Remember Me" field can't be checked in step 2 for the same reason.

This needs two patches in Capybara:

* https://github.com/teamcapybara/capybara/pull/1902
* https://github.com/teamcapybara/capybara/pull/1903

Add notes about database performance for MySQL

See merge request !13516

[ci skip]

fix confidential border issue as well as confidential styles leaking on new MR

Closes gitlab-ee#3121

See merge request !13388

Migrate force push check to Gitaly

See merge request !13406

Fixes the correct import modal window not showing

Closes #36318

See merge request !13490

Add option to disable project export on instance

See merge request !13211

Fix formatting of patch_versions.md

See merge request !13503

Better categorize test coverage results

See merge request !13485

Enable Timecop safe mode

Closes #32004

See merge request !13498

Better caching and indexing of broadcast messages

Closes #31706

See merge request !13429

Include the `is_admin` field in the `GET /users/:id` API when current user is an admin

Closes #36213

See merge request !13501

Make Git revision dropdown style consistent

See merge request !13116

Pending delete projects no longer return 500 error in Admins projects view

Closes #35435

See merge request !13389

Detect and keep track of flaky specs

See merge request !13021

Also marks a few things as uncovered, and removes an unused class.

Delete correct key from `session` after authenticating using U2F

Closes #36096

See merge request !13499

Caching of BroadcastMessage instances has been changed so a cache stays
valid as long as the default cache expiration time permits, instead of
the cache being expired after 1 minute. When modifying broadcast
messages the cache is flushed automatically.

To remove the need for performing sequence scans on the
"broadcast_messages" table we also add an index on (starts_at, ends_at,
id), permitting PostgreSQL to use an index scan to get all necessary
data.

Finally this commit adds a few NOT NULL constraints to the table to
match the Rails validations.

Fixes gitlab-org/gitlab-ce#31706

Use a separate table for storing push events

See merge request !12463