* Hide toggle behind feature flag
* Define component, update card logic, add graphQL mutation

The integration was done in https://gitlab.com/gitlab-org/gitlab/-/merge_requests/146002

Fetch data using mock query

EE: true

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

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

- Extends resolver with new argument disabled by default
- Updates existing and adds new specs
- Amends frontend GraphQL queries

Changelog: added
MR: https://gitlab.com/gitlab-org/gitlab/-/merge_requests/70126
EE: true

Integrate blob info query

This enables the ManageViaMr component for configuring Secret Detection.
It automates the creation of an MR via the GraphQL API.

This adds a new ManageViaMr component to the Security Configration page.
This component is for enabling a security feature via a merge request
via GraphQL.

This button is disabled by default behind the
sec_dependency_scanning_ui_enable feature flag.

Addresses https://gitlab.com/gitlab-org/gitlab/-/issues/325694 and
https://gitlab.com/gitlab-org/gitlab/-/issues/282533

.

Co-authored-by: Jannik Lehmann <jlehmann@gitlab.com>

Added blob content viewer to the app

Shows an alert for each failed site validation in the DAST profiles
library, along with a button to retry the validation, and a dismiss
button that revokes the validation.

Allow users to update existing Dast::Profiles.

- Clicking on `Generate code snippet` triggers a mutation to save the
configuration
- It also opens a modal containing a code snippet for the chosen
configuration
- User can simply copy the snippet to the clipboard and be redirected to
the code editor to apply the config

This updates the frontend so that the following queries and mutations
hit the actual API rather than local mocks:

- dastProfileCreate mutation
- dastProfileUpdate mutation
- dastProfiles query

Creates the form for configuring API fuzzing.

Hook the frontend for oncall deletions up
to the backend and activating the Apollo cache
allowing users to delete rotations

fix(feedback): apply merge feedback

Rather than skipping all queries that use the @client directive, we
instead remove all such fields (and any arguments and fragments
mentioned in the skipped sections) and then only skip the query if that
then leaves us with an empty query.

The query transformation is handled with a query printer.

This adds query validation for GraphQL, exposed in
a new raketask (`gitlab:graphql:validate`).

Tests are added for the validation system, which handles common patterns
in our front-end code (such as Apollo client directives, and the use of
ee_else_ce).

The new graphql files used in the tests are excluded from prettier
formatting.

A couple of clearly incorrect graphql files (discovered during testing)
have been fixed. One remaining one has been marked as a known failure.