Resolve "gitlab.com: Unable to import a project that was just exported"

Closes #43840, #43896, and #51747

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

Add clarity to EE feature styles for features introduced before and after 9.2

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

Resolve "Provide NullStore for RequestStore"

Closes #51718

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

Postgres alignment padding – logic fixed

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

Update ldap.md If you escape the '\' character when using a "domain\user" scheme for the bind_dn name, it will fail. gitlab-ctl reconfigure escapes characters, and if you pre-escape the '\', the resultant yaml file will have four (4) '\' characters

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

use redirect instead of render to avoid creating keys when refresh - resolves #47942

Closes #47942

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

Update frontend tooling dependencies

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

Refactor IDE index to support EE specific code

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

Use Vue component for job artifacts, Commit and Trigger Variables

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

Remove background job throttling feature

Closes #51509

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

**Why?**

- The web terminal feature is EE specific and will need to inject
  some specific options / functions into certain components.

* Fix typo in context 'when request store is active'
* Rearrange test since the instance variable always gets set now,
even if RequestStore is active

Even if it doesn’t save lines of code, since people will tend to use
code they’ve seen. And `SafeRequestStore` is safer since you
don’t have to remember to check `RequestStore.active?`.

These are clear wins.

Makes it easier and safer to use RequestStore because you don't need to
check `RequestStore.active?` before using it. You just have to use
`Gitlab::SafeRequestStore` instead.

Resolve "Collapsed open and closed sections in boards styling is broken"

Closes #51050

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

Post a commit note with the downstream pipeline URL for omnibus triggers

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

Refactor scripts/trigger-build and post a commit note with the downstream pipeline URL for omnibus triggers
Signed-off-by: Rémy Coutable <remy@rymai.me>

Auto devops docs improvements

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

We remove this feature as it never worked properly

Resolve "Resolved discussions automatically get unresolved when commented on"

Closes #24128

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

Feature/new user snippets breadcrumbs

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

**Why?**

The previous behavior had resolved discussions being unresolved
when commented on. This was strange UX, especially since there
is a separate button for "Comment & unresolve discussion".

https://gitlab.com/gitlab-org/gitlab-ce/issues/24128

**Note:**

- Also adds changelog

**Why?**
- These specs had duplicated code for a common context
- New specs for this context needs to be added

**Notes:**
- Also added some `wait_for_requests` to buttons that triggered AJAX

Move group labels AR code into finder

Closes #49653

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