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

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

Fixed crm db seed trying to seed non-root groups

See merge request gitlab-org/gitlab!83462

Clean up after fixing issue when admin changes email

See merge request gitlab-org/gitlab!83185

Resolve Rails/BelongsTo rubocop offenses

See merge request gitlab-org/gitlab!81382

The experiment has been deemed a failure so we should clean up the code
that implements it.

https://gitlab.com/gitlab-org/gitlab/-/issues/345553#note_866018518

Changelog: removed

Ensure custom notification mentions match UI

See merge request gitlab-org/gitlab!83661

Changelog: other
EE: true

Changelog: fixed

Force Host header rewrite in Workhorse for Geo proxying

See merge request gitlab-org/gitlab!83550

Update feature categories March 2022

See merge request gitlab-org/gitlab!83672

Merge branch '354335-project-transfers-to-personal-namespace-does-not-create-membership-for-the-owner' into 'master'

Resolve "Project transfers to personal namespace does not create membership for the owner"

See merge request gitlab-org/gitlab!83175

Add VSA empty state component to base component

See merge request gitlab-org/gitlab!83712

This is fix users whose primary emails is not in Email table;
that used to happen when admin changed user primary email.
That behavior was fixed, now we want to fix the affeted users

Changelog: other

Merge branch '352969-security-policy-definition-not-respected-with-scheduled-scan-action' into 'master'

Don't include compliance pipeline definition in scheduled security orchestration pipelines

See merge request gitlab-org/gitlab!82613

EE: true
Changelog: fixed