Document repository tag deletion limit

See merge request gitlab-org/gitlab!83704

Refactor environment empty state to use scope

See merge request gitlab-org/gitlab!83422

Fix external links in development docs

See merge request gitlab-org/gitlab!83719

Merge branch 'morefice/ui-should-explain-if-no-junit-report-artifacts-are-available-to-populate-unit-test-report' into 'master'

Render errors if test report artifacts are expired

See merge request gitlab-org/gitlab!83113

This commit exposes a new attribute to our TestSuiteEntity
which will be used to determine when junit artifacts have
expired when displaying TestCases.

Define class for logged_out_marketing_header experiment

See merge request gitlab-org/gitlab!83714

Sleep between inserting batches of refreshes

See merge request gitlab-org/gitlab!83622

Update copy for DAST Profiles library page

See merge request gitlab-org/gitlab!83375

Update Content Editor Packages

See merge request gitlab-org/gitlab!82586

Adjust icons and button wording for license compliance

See merge request gitlab-org/gitlab!83703

The empty state reported that you didn't have any environments
regardless of scope, which was a bit misleading if you had many
available environments and no stopped environments.

I have refactored the component to allow the scope to be injected so the
text can change depending on what scope the user is looking at.

I've also refactored the rest of the translations to follow more
up-to-date patterns, and rewritten the tests to utilize the testing
library's queries for finding things by role.

Changelog: fixed

Added read_usage_quotas ability to ProjectPolicy

See merge request gitlab-org/gitlab!82396

Cleanup secret variables refactoring in variables builder

See merge request gitlab-org/gitlab!83428

Cleanup api_kaminari_count_with_limit

See merge request gitlab-org/gitlab!81084

Changelog: removed

FIPS SSH key configuration settings

See merge request gitlab-org/gitlab!81917

Changelog: other

Clean up code for invite_team_email experiment

See merge request gitlab-org/gitlab!82799

Crosslink other rate limits for GitLab.com

See merge request gitlab-org/gitlab!83615

Show description text for "Users in Subscription" card for Ultimate plans only

See merge request gitlab-org/gitlab!81286

Changelog: changed
EE: true

Migrate to GlAlert in Pages Domains form

See merge request gitlab-org/gitlab!83694

Raise exception when gitaly-backup could not be found

See merge request gitlab-org/gitlab!83555

Update API doc to show correct return type

See merge request gitlab-org/gitlab!81895

Period limit default Insights yaml

See merge request gitlab-org/gitlab!83718

EE: true
Changelog: changed

Add empty state for Instance OAuth app page

See merge request gitlab-org/gitlab!83279

Enqueuer job: fix the re enqueue

See merge request gitlab-org/gitlab!83527

Fix PA for projects in nested groups

See merge request gitlab-org/gitlab!83282

Fix artifacts content-type

See merge request gitlab-org/gitlab!83515

Fix project permission toggle behavior

See merge request gitlab-org/gitlab!83503

Problem:

```
Given that you are on public project
When you disable a permission
  And enable it again
Then the dropdown shows that you selected the last value on the list
While the internal input has another value set.
```

This has to do with a quirky behavior where we replace the `value` and
the `options` provided to the `<select>` inside of the
ProjectFeatureSettings input component. Internally we used the
`selected` attribute of the `<option>` elements to track which option
was selected. That attribute is just for initial rendering though:

> If present, this Boolean attribute indicates that the option is
> initially selected. If the `<option>` element is the descendant of a
> `<select>` element whose multiple attribute is not set, only one
> single `<option>` of this `<select>` element may have the selected
> attribute.

This seems to be non-problematic if one never changes the options that
are availabe for the specific select.

The solution for this is to create a computed property with a getter and
setter and use that computed property as a v-model for the internal
select.

Changelog: fixed

Fix project permission toggle behavior

See merge request gitlab-org/gitlab!83503

Problem:

```
Given that you are on public project
When you disable a permission
  And enable it again
Then the dropdown shows that you selected the last value on the list
While the internal input has another value set.
```

This has to do with a quirky behavior where we replace the `value` and
the `options` provided to the `<select>` inside of the
ProjectFeatureSettings input component. Internally we used the
`selected` attribute of the `<option>` elements to track which option
was selected. That attribute is just for initial rendering though:

> If present, this Boolean attribute indicates that the option is
> initially selected. If the `<option>` element is the descendant of a
> `<select>` element whose multiple attribute is not set, only one
> single `<option>` of this `<select>` element may have the selected
> attribute.

This seems to be non-problematic if one never changes the options that
are availabe for the specific select.

The solution for this is to create a computed property with a getter and
setter and use that computed property as a v-model for the internal
select.

Changelog: fixed

Add Submit Vulnerability button to empty page

See merge request gitlab-org/gitlab!83597

When the user has the necessary permissions, display a button
to create a vulnerability manually.

Resolve "Follow-up from "Implement API to get single MR rule""

See merge request gitlab-org/gitlab!83501