This commit removes the feature flag guarding this feature, making it
available for general consumption, and updates the documentation to
suit.

- This replaces several instances
of the fa-file-text-o fontawesome
icon with the GitLab SVG doc-text icon

This updates doc/user/application_security/dast/index.md
and corresponding tooltips in the scanner profile form

Added modal and controls components for
overall editing merge request metadata

Add the ability to disable shared runners
on a group level via the UI.

Update fetching of issues in GraphQL to paginate issues in lists

Expose file from test case entity
Add file to fixture and mock_data
Display file in table

- Also wrapped snippet_show in DOMContentLoaded
- Also fixes full screen comment button on snippets

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

The new report type uses the Dast report parser
as the schema is shared between API Fuzzing and DAST.

* Update the backend code
* Update GraphQL schema
* Update related tests
* Add sample report to test assets

Adds icons and tooltips to status column on alerts integrations list

Created the auto-fix user callout that shows up in the project security
dashboard (unless previously dismissed).

Hide vulnerability after dismissal if not in filter list and process
each dismissal instead of stopping after the first failure

* Add additional fields

This would allow users to choose scan type,
and option to enable ajax spider and debug
messages for On-demand Scan Profiles

This reverts merge request !41430

When a user attempts to destroy a Web hook, the database will attempt to
delete all the associated Web hook logs. However, as we have seen in
https://gitlab.com/gitlab-org/gitlab/-/issues/21940, the table may be
too bloated or the number of rows too large that this deletion can time
out due to a 15-second statement timeout.

We rectify this situation by deleting these logs in batches of 1000
outside of a transaction. That should be acceptable since old logs get
pruned periodically anyway, and when a Web hook is destroyed it's more
important that the destruction makes progress and eventually removes the
hook.

Relates to https://gitlab.com/gitlab-org/gitlab/-/issues/21940

- source
- tests

This MR adds warning state in the usage quota
table if a project storage is in warning state.
The changes are behind a feature flag. A tooltip
is also added to the warning icon

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

- This has been enabled for a while and
the tests have been updated.
- Also removes snippet_bundle which isn't
referenced anymore.
- Also removes unused CSS.

Part of a larger initiative to convert the group members view from
HAML to Vue

Also add toggle to load old data
We now also render the charts before making the network request
for both cases, which speeds up the rendering of charts
Add a flag to ensure we only fetch burndown data once

Adds a d3 implementation that takes all the
yaml visualization nodes and trace lines
between those who are needed.

Adds logic to handle pending and in-progress states when a profile
gets edited.

Update ee/app/assets/javascripts/vue_shared/security_reports/components/solution_card.vue, ee/spec/frontend/vue_shared/security_reports/components/modal_spec.js files

This aligns the signup with the trial signup and what
Growth::Acquisition has built as a signup experiment.

- source
- tests
- snapshots

This feature flag was introduced by:

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/19451

and was made default by:

https://gitlab.com/gitlab-org/gitlab/-/merge_requests/27032

It is now safe to remove.

Build the lint results
in Vue and setup apollo.
Add test coverage for components.

It was enabled by default in GitLab 13.1 in
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/33998
and no issues were seen.