Addresses https://gitlab.com/gitlab-org/gitlab/-/issues/332691.

Remove webhooks_moved notice from Integrations page.

Introduced in %"12.9" with
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/23136
and can now be removed.

Changelog: changed

Was introduced before %"13.0" and can now be removed

The getAlert function searches through all available alerts (added
previously), returning the first alert where its show function returns
true, or null if none is found.

Actions to fetch the CI configuration for its given current
content (when it is being edited), as well as to dismiss the callout for
environment guidance are added here.

We parse the CI configuration during the mutation to only retain whether
or not we have:

- sucessfully parsed the CI config, and
- found an environment within the config.

To enable us to show a new pipeline banner
for needs view, we need a new enmu value
for the user callouts.

Adds global callout for admin users, explaining that
they should migrate to Integrations.

This commit also adds a spec for the callout.

The maximum number of user callouts for a single user
is limited by the number of different types of callouts

At the moment we have 28, so it ok to load all these
lightweight records instead of making a separate request
for every feature

Renamed variables, constants and traits in rspecs

This also helps persist when the banner has been
dismissed

- project
- group
- bundle.js

Add banner for notyfing admins about reached
cap for new user signups.

Shown only to admins to let them know that anybody can register on
their instance

As we have chosen a simple editor approach for editing of the GitLab CI
yml file, we want to remove the benner that suggests it to our users.

This commit largely reverts 52ad6ade

Since the recommendation is to define all enums in FOSS, move the EE
only enums into FOSS. Since the enums were moved into concerns so that
it is easier to extend the Hash in EE, this commit moves all the enums
back into the model.

Move enums related modules into a separate directory.

This reverts merge request !38061

Move enums related modules into a separate directory.

Introduces support for tracking dismiss of callouts
Check callouts is shown every 3 months

In a few models we define ActiveRecord enums that are redefined in EE
using the following pattern:

    enum :some_enum, {
      ...
    }.merge(EE_ENUM_VALUES)

This particular approach is problematic to deal with, because it
requires that we `prepend` and EE module _before_ defining the enum.
This typically translates to the `prepend` being the first line in the
model in EE, but this can easily lead to merge conflicts when developers
add more `include` and/or `prepend` lines.

As part of https://gitlab.com/gitlab-org/gitlab-ee/issues/8244 and
https://gitlab.com/gitlab-org/gitlab-ee/issues/8241 we are moving
`prepend` to the last line in a file, reducing the chances of running
into merge conflicts. This poses a bit of a problem with the pattern
above, because this pattern does not allow us to move the `prepend`
further down a file.

To resolve this problem, we simply move the Hash value of the enum to a
separate class method. This method is defined in a separate module where
necessary, allowing us to use it like so:

    enum :failure_reasons, ::SomeModelEnums.failure_reasons

The method in turn is defined in a very straightforward manner:

    module SomeModelEnums
      def self.failure_reasons
        {
          ...
        }
      end
    end

This makes it easy for EE to add values without requiring the `prepend`
to be placed before the `enum` is defined.

For more information, see the following issues and merge requests:

* https://gitlab.com/gitlab-org/gitlab-ee/issues/8244
* https://gitlab.com/gitlab-org/gitlab-ee/issues/8241
* https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8424

In a few models we define ActiveRecord enums that are redefined in EE
using the following pattern:

    enum :some_enum, {
      ...
    }.merge(EE_ENUM_VALUES)

This particular approach is problematic to deal with, because it
requires that we `prepend` and EE module _before_ defining the enum.
This typically translates to the `prepend` being the first line in the
model in EE, but this can easily lead to merge conflicts when developers
add more `include` and/or `prepend` lines.

As part of https://gitlab.com/gitlab-org/gitlab-ee/issues/8244 and
https://gitlab.com/gitlab-org/gitlab-ee/issues/8241 we are moving
`prepend` to the last line in a file, reducing the chances of running
into merge conflicts. This poses a bit of a problem with the pattern
above, because this pattern does not allow us to move the `prepend`
further down a file.

To resolve this problem, we simply move the Hash value of the enum to a
separate class method. This method is defined in a separate module where
necessary, allowing us to use it like so:

    enum :failure_reasons, ::SomeModelEnums.failure_reasons

The method in turn is defined in a very straightforward manner:

    module SomeModelEnums
      def self.failure_reasons
        {
          ...
        }
      end
    end

This makes it easy for EE to add values without requiring the `prepend`
to be placed before the `enum` is defined.

For more information, see the following issues and merge requests:

* https://gitlab.com/gitlab-org/gitlab-ee/issues/8244
* https://gitlab.com/gitlab-org/gitlab-ee/issues/8241
* https://gitlab.com/gitlab-org/gitlab-ee/merge_requests/8424

Show a dismissable callout on a users dashboard for a free trial of
the GitLab.com Gold plan. Hide the callout from users who have
dismissed the callout, are already on a trial or are already on the
gold plan

This reverts merge request !21551

Partially addresses #47424.

Partially addresses #47424.