New component, feature-card-badge, is displayed on DAST
configuration card. It is shown based on feature configuration.
New property "badge" can be added to
a specific feature via backend or frontend.
Layout of the card is adjusted accordingly
based on configuration. Specs are adjusted accordingly.
feature-card-badge has internal logic for conditional
tooltip rendering.

Changelog: changed
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/83723
EE: true

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

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

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 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

This new component represents a given feature for the redesigned
Security & Compliance Configuration page.

Addresses https://gitlab.com/gitlab-org/gitlab/-/issues/328385, part of
https://gitlab.com/groups/gitlab-org/-/epics/5820.