Fix Error 500 when viewing a merge request with a deleted source project

Closes gitlab-ce#33011

See merge request !1996

Fixed header being over issue boards in focus mode

Closes #2473

See merge request !2002

Closes #2473

Port of 31849-pipeline-show-view-realtime to EE

See merge request !1990

EE - Add performance deltas between app deployments on Merge Request widget

See merge request !2001

Fix locked milestone in boards being remove-able

Closes #2433

See merge request !1963

Resolve "Assignee dropdown does not display selected assignee"

Closes #2472

See merge request !1968

Allow saving no plan on namespaces

Closes #2482

See merge request !1993

[CE Backport + ES implementation]Resolve "Wiki is not searchable with Guest permissions"

See merge request !1964

[EE] New Migration/UpdateColumnInBatches cop

See merge request !1999

Fix: Approvals not reset if changing target branch

See merge request !1941

Set EE_PACKAGE variable for triggers

See merge request !1982

Add per page to user autocomplete (EE)

See merge request !1991

Fix up some notes tech debt -- EE merge edition

See merge request !1911

Remove double `gitlab_usage_ping_worker` cron job

See merge request !1998

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

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

If the merge request can be rebased based on the history of the commits,
users attempting to view the merge request would hit an Error 500. This
occurred because `user_can_push_to_source_branch?` would be called
on a non-existent project.

Closes gitlab-org/gitlab-ce#33011

Fix failing EE builds due to blacklisted Web connections

Closes #2507

See merge request !1995

Fix bug where files over 2 GB would not be saved in Geo tracking DB

See merge request !1992

If unicorn_spec.rb were run before Elasticsearch specs, it would
disable all outbound network connections, which would prevent the
latter from being able to communicate with Elasticsearch in CI. To
fix this, we restore the original WebMock settings after finishing
the spec.

Closes #2507

If an LFS file were over 2 GB, Sidekiq would fail with a message such as:

```
2917923200 is out of range for ActiveRecord::ConnectionAdapters::PostgreSQL::OID::Integer with limit 4
```

To fix, increase the value in the database from a 4-byte integer to a 8-byte integer.