Fix logic to determine export status

Closes #32203

See merge request gitlab-org/gitlab!23664

204774 Quick actions executed in multiline inline code, when placed on it's own line

Closes #204774

See merge request gitlab-org/gitlab!24933

Migrate blob_file_dropzone to jest

See merge request gitlab-org/gitlab!26776

Migrate ee/spec/javascripts/prometheus_metrics/ to Jest

Closes #194301

See merge request gitlab-org/gitlab!27012

Improve NPM api tests execution time

See merge request gitlab-org/gitlab!26810

Design view: better resizing support for zoomed-in designs

See merge request gitlab-org/gitlab!25406

Consider flags enabled when generating GraphQL schema

See merge request gitlab-org/gitlab!26939

Add organization transition to Jenkins doc

See merge request gitlab-org/gitlab!26897

Update pipeline copy on dependency & license compliance pages

See merge request gitlab-org/gitlab!26864

Currently, lock files are used to determine the state of a
project export. However, the lock files are not stored in a shared
volume, causing the export states to be reported incorrectly.

In order to fix this, we now store the export states in database
as a more reliable mechanism. The table used is project_export_jobs.
It stores the project_id, job_id and the current state.

In addition to existing states, also added are two new states
queued and regeneration_in_progress states. They are used to indicate
a job that's waiting to be started and the case when a project export
operation has been requested to be re-generated.

Failed jobs are re-tried 3 times, after which the state is updated
to failed.

To account for jobs that get stuck, a cron job runs every hour
to set the stuck jobs to failed state.

Closes https://gitlab.com/gitlab-org/gitlab/issues/32203

Remove reference to subject label

See merge request gitlab-org/gitlab!26928

- Subject labels look to have been renamed previously to feature labels.
- I also noticed that Blue is widely used across all different types of
labels so I removed that requirement from this workflow as well.

Fix mermaid flowchart width

Closes #199132 and #199423

See merge request gitlab-org/gitlab!26848

Upgrade AWS SDK dependency

See merge request gitlab-org/gitlab!27003

Migrate ee vue_mr_widget/mr_widget_pipeline_spec from Karma to Jest

See merge request gitlab-org/gitlab!26707

Change tilde codeblocks to quad backticks

See merge request gitlab-org/gitlab!26994

Check for incorrect extension on internal links

See merge request gitlab-org/gitlab!26627

Linking between Deploy keys/Deploy tokens topics

Closes #209692

See merge request gitlab-org/gitlab!26809

Make vale use raw scope

See merge request gitlab-org/gitlab!27044

Allow multiple descriptionVersions

See merge request gitlab-org/gitlab!26316

Remove unused code in Geo::PruneEventLogWorker

See merge request gitlab-org/gitlab!26621

Use full qualified class name in pod logs services

See merge request gitlab-org/gitlab!27043

Fix capitalization issues

See merge request gitlab-org/gitlab!27049

Create a single temporary index for note mentions migration

See merge request gitlab-org/gitlab!26307

Geo docs: Add troubleshooting help for gitlab-pg-ctl

See merge request gitlab-org/gitlab!26701

When scale is 1, add the `img-fluid` class
and re-set the base image size.

This way, the image can better respond to window resizes

Docs: Caution to backup first before opting in

See merge request gitlab-org/gitlab!27037

If they have an existing DB, then they need to first
dump their DB before opting in.

Enable VSM feature flag for code stage by default

Closes #202094

See merge request gitlab-org/gitlab!26885