Map jira users for server version by 'key' attribute

See merge request gitlab-org/gitlab!66670

Migrate Edit Environments Form to Vue

See merge request gitlab-org/gitlab!66573

Improves find function virtual scrolling disabling

See merge request gitlab-org/gitlab!66629

The readme checkbox for new projects is checked by default

See merge request gitlab-org/gitlab!66558

Use nullify_if_blank for Environment#external_url

See merge request gitlab-org/gitlab!66589

Revert "Merge branch '36118-add-linked-pipeline-mini-list-to-pipelines-table-component' into 'master'" to fix foss master broken [RUN-AS-IF-FOSS]

See merge request gitlab-org/gitlab!66704

Docs: Add note that direct fetch FF is required

See merge request gitlab-org/gitlab!66392

Handle post processed content scenario for MR discussions cache

See merge request gitlab-org/gitlab!66354

Bump gitlab-omniauth-openid-connect to v0.8.0

See merge request gitlab-org/gitlab!65782

Use a dedicated project access token for CI scripts

See merge request gitlab-org/gitlab!66628

Docs: Note 'repo scoped: invalid Repository' errors

See merge request gitlab-org/gitlab!65264

Blob refactor: Fix the Auxiliary viewers

See merge request gitlab-org/gitlab!66529

We cache MR discussions after post processing. Before this fix, we
aren't considering the post processing result (e.g. reference state
change) which results to stale cache.

This fix adds a `Note#post_processed_cache_key` that is also added
to `Discussion#cache_key`. This way, when the post processing
changes the note's content for a certain user, we will be able to
show updated content.

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

Revert "Merge branch '36118-add-linked-pipeline-mini-list-to-pipelines-table-component' into 'master'"

This reverts merge request !66274

Add CodeQuality sample configuration for private image registries

See merge request gitlab-org/gitlab!65997

Polish tab count and create button in test cases

See merge request gitlab-org/gitlab!66608

Update access token tier and version info

See merge request gitlab-org/gitlab!66645

Ignore full path matches when searching groups in REST API

See merge request gitlab-org/gitlab!66431

Delete examples that only pass on retries

See merge request gitlab-org/gitlab!66606

Merge branch '336214-bulk-dismissal-checkboxes-don-t-appear-on-group-vulnerability-report' into 'master'

Resolve "Bulk dismissal checkboxes don't appear on group vulnerability report"

See merge request gitlab-org/gitlab!66312

Merge branch '335982-add-loading-state-and-form-hiding-on-error-to-group-level-merge-request-settings' into 'master'

Add loading icon and form hiding on error to group-level merge request settings

See merge request gitlab-org/gitlab!66154

Remove merge_request_draft_filter feature flag

See merge request gitlab-org/gitlab!66507

Create 14.1 What's new entry

See merge request gitlab-org/gitlab!66570

Resolve "Slow ci runners query at /api/:version/runners"

See merge request gitlab-org/gitlab!66352

Add new BulkImports endpoint to start new migration

See merge request gitlab-org/gitlab!66353

  - Currently the only way to start BulkImport GitLab
    migration is to do that via the UI
  - Add new endpoint to be able to do the same thing
    via the API

Changelog: added

Use the configured redis DB in specs that run workhorse

See merge request gitlab-org/gitlab!63632

Convert old GraphQL types to newer type names (Part 2) [RUN AS-IF-FOSS]

See merge request gitlab-org/gitlab!66462

In Jira Cloud user identifier is returned in 'accountId' attribute
while in Jira Server it is being returned in 'key' attribute. This
fixes the user mapping for jira issues import from Jira Server instance.

Changelog: fixed

Add updated_at index to improve Merge Request API performance

See merge request gitlab-org/gitlab!66594

Resolve "Allow Guests to download packages from private projects"

See merge request gitlab-org/gitlab!66567

Re-uses the new form component made as part of the migration of new
environments.

There was some question about whether or not we need Vuex or something,
but honestly because the form manages such a low number of properties
and the validation requirements are so small, that I opted to not use it
here instead.

Also the environment model is small, and so can be inlined in a data
attribute. As the validation is stricter on the backend, this should be
clear of HTML injection.

Changelog: changed