In various user-facing templates and messaging, update the outdated
MWPS language to instead use auto-merge. These changes make ancillary
pieces of the product more accurately reflect what the user now sees
in the UI.

Changelog: changed

Changelog: changed
EE: true

Remove require_verification_for_namespace_creation feature
flag and experiment file

Changelog: removed

Changelog: changed
EE: true

- only ever used in ee and never used in foss

Fix rubocop offenses

Changelog: other

- method is deprecated

- make part of product

Changelog: changed
EE: true

This fixes all non-test file offenses

Add high-converting security trial actions
to continuous onboarding

Changelog: added

This commit fixes a couple of linting issues in the new project
README template.

Previously, Users::InProductMarketingEmail was used to track sending of
track+series (onboarding) emails. Here, we update the model to
track campaign emails (e.g. Build iOS app guide email) and track+series
(onboarding) emails.

Used for the ios_specific_templates experiment

This introduces a new checkbox on project creation, and cleans up the
new_project_sast_enabled experiment that tested the usefulness and
engagement of that checkbox.

Changelog: added

- Create video_tutorials_continuous_onboarding experiment feature flag
- Publish experiment in LearnGitlabController
- Add a button top open videos in a new tab from learn_gitlab
- Track click to video in candidate flow of experiment
- Make learn_gitlab_section_card responsive
- Update snaphost & unit tests for learn_gitlab

We’ve removed the concept of using `window.gon` in the client, so we can
now remove the publishing overrides that were keeping that logic. We
also remove the `#publish_to_client` method to encourage calling the
`#publish` method directly.

We were using public behavior methods, which is deprecated. Instead,
register the experiment behaviors in the classes, which lets them be
understood at the time the experiment is run or published.

This is because all experiments are so far circumventing the rule, as
well as they may span an area of focus. The experiment feature flags
can be useful for this, or we can choose to solve this challenge in a
different and more nuanced way.

This provides a default rollout strategy for experiments. The idea is to
provide a cleaner abstraction for the logic required to add any number
of rollout strategies over time.

This reverts commit 6d4d3531, reversing
changes made to a125e8fb.

Changelog: fixed

This reverts merge request !78987

Credit card verification experiment should only be enabled for users
created _after_ the experiment was made active.

This also introduces a new way to configure the readme template on new
project creation which can be used by other services like the
`Projects::CreateService`. It utilizes ERB for customizing the contents
of the readme templates.

Changelog: added

This adds an experiment for requiring credit card validation
before creating a new group when signing up.

Changelog: added

- This fixes an issue with assigning this variant.

The `force_company_trial` experiment has been marked as a loser and this
MR is responsible for removing it.

* The `combined_registration` experiment will continue to use
  "force_company_trial" in it's context key as it is still running and
  there are conversions that we are still possible

part of:
https://gitlab.com/gitlab-org/gitlab/-/issues/345621

Changelog: removed

- This passes through known experiment context keys to the track call so
they can be utilized by the gitlab standard context if supported.

- Deprecates the usage of `publish_to_database` as well

- This makes nesting experiments more flexible, but can still surface in
reporting.