This commit refactors the security configuration
data accumulation to be consistent across CE & EE.

* Adjust text based on feedback

This commit adds a backend call (GraphQL) mutation, which
dismisses the promotion callout for the security-training feature,
when a user enables the training within the config.

Changelog: added
EE: true

This change switches from using mock, client-side resolvers for
retrieving security training providers, to fetching the data from
the actual GraphQL endpoint.

- Track when the banner is rendered (mounted)
- Track when the banner is closed (dismissed)
- Track when the banner CTA is clicked
- Update associated tests

Configuration History should not exist when
CI config is not present. Auto Devops button
should be present. As per bugfix MR
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70025

This commit adds error handling to the security-training
providers configuration page.

* Refactor existing usages

Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/346488

Issue: https://gitlab.com/gitlab-org/gitlab/-/issues/347414

This extracts the code that maps scanner names to their translations
into a dedicated helper.

This slightly changes how the scanner names' translations are being
gathered before being passed to the security-scanner-alert component.
By moving all the translation to a shared map, it should harder to
forget to provide a new translation when adding a new scanner.

This is primarily done to translate SAST_IAC to something more
user-friendly.

Changelog: fixed

Refactor apollo query into TrainingProviderList component
and update specs accordingly.

Address reviewer comment and adjust to use client directive

Utilize the loading skeleton when trainers are being fetched

This removes the `configureIacScanningViaMr` feature flag that was
enabled by default in 14.6.

Changelog: removed

Add security training ui to security configuration.
This is within the vulnerability management tab.

This ensures that the UI links to the proper documentation pages for IaC
Scanning.

This moves the FE code for configuring IaC Scanning back to CE.

This adds the IaC Scanning configuration card to the Security
Configuration page.

- Fixed all the occurences of 'createDefaultClient'
- Updated FE guide on Apollo immutability

As per https://gitlab.com/gitlab-org/quality/testcases/-/issues/1666
The functionality was introduced, this MR
adds an End to End test to test this

* Add row to configuration page for corpus management

This commit solves: https://gitlab.com/gitlab-org/gitlab/-/issues/326005
It removes the sec_dependency_scanning_ui_enable Feature Flag
which was enabled by default in 14.1

Changelog: removed

This commit solves https://gitlab.com/gitlab-org/gitlab/-/issues/331276
It enables `assumeImmutableResults` in the security_configuration index

This should make the suite pass regardless of the state of the
`security_configuration_redesign(_ee)?` feature flags.

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

This MR solves: https://gitlab.com/gitlab-org/gitlab/-/issues/334927
It changes the copy for the upgrade banner on the
security configuration Page.

This also makes sure that the configuration guide link is only displayed
for a given feature if that feature has a configurationHelpPath
property.

This makes sure that the "Configure via Merge Request" button is
displayed for Secret Detection in the [new][1] Security Configuration
page for all tiers.

The button was not working in FOSS since the client-side mutation was
only defined in EE, so that was moved to FOSS. The backend
implementation of the mutation is already in FOSS.

This also ensures that a similar button is displayed for Dependency
Scanning in Ultimate projects when the sec_dependency_scanning_ui_enable
feature flag is enabled.

Addresses https://gitlab.com/gitlab-org/gitlab/-/issues/326005 and
https://gitlab.com/gitlab-org/gitlab/-/issues/328426.

[1]: https://gitlab.com/gitlab-org/gitlab/-/issues/326926

Changelog: fixed
EE: true