Export JS classes as modules

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

Don't use Markdown cache for stubbed settings in specs

Closes #41130

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

Make help link open in new tab

Closes #41073

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

Rename QA scenarios to make factory concept explicit

Closes gitlab-qa#86

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

Add SAST docs

Closes gitlab-ee#4125

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

Make sure user email is read only when synced with LDAP

Closes #41033

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

Fix UX issues in system info page

Closes #38145

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

Update svg package version

Closes #41014

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

Change text from build to job in flash notice

Closes #41136

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

Add note about automatic pipelines when enabling Auto DevOps

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

fix formatting of parameters for new group and transfer project to group

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

Simplify conflict resolver interface

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

Docs update documentation guidelines

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

fix button alignment on MWPS component

Closes #38541

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

The ApplicationSetting model uses the CacheMarkdownField concern, which updates
the cached HTML when the field is updated in the database. However, in specs,
when we want to test conditions using ApplicationSetting, we stub it, because
this is accessed in different ways throughout the application.

This means that if a spec runs that caches one of the Markdown fields, and a
later spec uses `stub_application_setting` to set the raw value of that field,
the cached value was still the original one. We can work around this by ignoring
the Markdown cache in contexts where we're using `stub_application_setting`.

We could be smarter, and only do this on the Markdown fields of the model, but
this is probably fine.

Import gitlab-shell gitlab_projects.rb as at v5.10.2

Closes #41016

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

#38869

Add eager-load paths to autoload paths to fix Rake tasks

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

Added LFS badge to indicate LFS tracked files

Closes #15567

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

Pass info regarding the user and job that initiated a trigger

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

This does two things:
- Pass commit oids instead of `Gitlab::Git::Commit`s. We only need the
former.
- Depend on only the target repository for conflict listing. For
conflict resolution, treat one repository as a remote one so that we can
implement it as such in Gitaly.

Migrate Gitlab::Git::Repository#merge_base_commit to Gitaly

Closes gitaly#808

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

Docs: add indexes for monitoring and performance monitoring

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