Add Jira status to Jira issues

See merge request gitlab-org/gitlab!36924

- Expose Jira status from backend
- Show Jira status in place of GitLab's "closed" status

Add additional specs for Section support

See merge request gitlab-org/gitlab!36897

Remove need to call gitaly in ProjectPipelineStatus

Closes gitlab-foss#52780

See merge request gitlab-org/gitlab!33712

Improve parallel persistance for audit event author_name

See merge request gitlab-org/gitlab!36826

Merge branch '208655-annotate-non-deployment-jobs-with-prepare-keyword-on-environment-action-keyword' into 'master'

Add docs for `prepare` keyword on `environment:action:` keyword

See merge request gitlab-org/gitlab!36568

Remove feature flag docs for Confluence service

See merge request gitlab-org/gitlab!36919

With the feature flags removed in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/36781, this
change updates the documentation to reflect this.

https://gitlab.com/gitlab-org/gitlab/-/issues/220934
https://gitlab.com/gitlab-org/gitlab/-/issues/228731

Update Rouge to v3.21.0

Closes #220566

See merge request gitlab-org/gitlab!36942

Make sure end-to-end tests use unique filenames in template tests

Closes #227029 and #210504

See merge request gitlab-org/gitlab!36835

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

Make related issues component more extendable

See merge request gitlab-org/gitlab!35598

Make the related issues component used on the Issues page more
extendable so that it can be reused on the standalone vulnerabilities
page

Enable BulkInsertSafe on Ci::BuildNeed

See merge request gitlab-org/gitlab!36815

Merge branch '221013-add-instance-setting-for-default-initial-branch-name-for-new-repositories' into 'master'

Set feature flag `global_default_branch_name` to default to true

See merge request gitlab-org/gitlab!36889

Store reason for resource state events

See merge request gitlab-org/gitlab!32924

Also update specs and add needed fields for source of state change to
resource_state_events table.

Enable raw stackprof collection for flamegraphs

See merge request gitlab-org/gitlab!36022

Also add documentation on how to generate flamegraphs.

Removes "fixes" that broke the pipeline table

Closes #36383

See merge request gitlab-org/gitlab!36803

Add deploy keys to protected branches (DB and API)

See merge request gitlab-org/gitlab!34875

GraphQL docs - lowercase iteration's `include_ancestors` description

See merge request gitlab-org/gitlab!36870

Expose blob mode in GraphQL for repository files

See merge request gitlab-org/gitlab!36488

On verification of https://gitlab.com/gitlab-org/gitlab/-/issues/220318
we discovered that some audit events were not created with
author_name populated correctly.

This approach saves the author_name as an AR callback instead.

Add 'Code Owners' section to CODEOWNERS

See merge request gitlab-org/gitlab!36887

Calling commit (gitaly) is un-nessary just to obtain the sha, for the
cache key. In fact, the cache key does not need to have the sha as the
sha is part of the cache value. The new cache key should be unique
enough for each project.

This saves us 20 gitaly calls on the dashboard page (assuming we have
one full page of projects).

Add scanned_resources CSV path to Security Report Summary

See merge request gitlab-org/gitlab!36810

Merge branch '220573-frontend-modify-secure-configuration-page-to-provide-entry-point-to-sast-config-ui-page-2' into 'master'

Add button to Security Configuration to enable SAST scanning

See merge request gitlab-org/gitlab!36432

This adds a button to the Security Configuration page, allowing the user
to enable SAST scanning via a merge request with a simple click. This
button is only displayed when:

1. The sast_configuration_by_click feature flag is enabled.
1. The project does not have an existing .gitlab-ci.yml file.

Some other changes include (and are _not_ behind any feature flag):

 -  Add third status text string for when Auto DevOps is enabled.
 -  Add third column headed "Manage" to the Security Configuration
    table, which contains a link to that scanner's documentation. This
    is where the button appears in the SAST case when the
    sast_configuration_by_click feature flag is enabled.
 -  Extract thClass constant in app component.
 -  Do not guard the SASTConfigurationController#create action behind
    the sast_configuration_ui feature flag. This feature flag is
    intended for a future iteration when an actual configuration UI
    exists for SAST, which is what that controller is actually for. In
    this iteration, it's simply a placeholder for the temporary REST
    endpoint, which will be [replaced][gql] by a GraphQL mutation in
    another iteration.

This is an MVC for creating a [Configuration UI for SAST][1]. Some
technical debt has been incurred here:

1. The REST (POST) endpoint used to create the merge request will be
   replaced by a [GraphQL mutation][gql].
1. The `type` of each feature has been added to the security
   configuration features exposed to the fronted. This should be
   [replaced][type] by a field exposing the scanner's configuration UI
   path (or similar).
1. The CreateMergeRequestButton component will likely be removed in the
   next iteration of the SAST Configuration UI, particularly if the
   GraphQL mutation is ready by then.

Addresses https://gitlab.com/gitlab-org/gitlab/-/issues/220573, part of
[Configuration UI for SAST][1].

[1]: https://gitlab.com/groups/gitlab-org/-/epics/3262
[gql]: https://gitlab.com/gitlab-org/gitlab/-/issues/227465
[type]: https://gitlab.com/gitlab-org/gitlab/-/issues/227575

Clarify changelog docs for feature flags

See merge request gitlab-org/gitlab!36276

Update $gray-900 to match gitlab-ui palette

Closes #228727

See merge request gitlab-org/gitlab!36778

Removing unused symbol folder

See merge request gitlab-org/gitlab!36858