Updates form to use shared components like PageHeading,
SettingsSection and Crud.

Changelog: changed

This commit:
- Implements multi-threaded DuoChat integration
- Updates all GraphQL queries required for the multi-threaded architecture.
- Ensures seamless fallback to single-threaded mode when duo_chat_multi_thread is disabled.
It was initially merged in:
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/179708


Reverted to some breaking-changes in the API
that are resolved.

EE: true

Merged-by: Jannik Lehmann <jlehmann@gitlab.com>
Approved-by: Lindsey Shelton <lshelton@gitlab.com>
Approved-by: Andrew Fontaine <afontaine@gitlab.com>
Reviewed-by: Andrew Fontaine <afontaine@gitlab.com>
Reviewed-by: Jannik Lehmann <jlehmann@gitlab.com>

Correct data setting and
store initialisation

EE: true

Update the vulnerability details page to use shared
dependency_path_drawer component.

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

This reverts merge request !179708

- Implements multi-threaded DuoChat integration
- Updates all GraphQL queries required for the multi-threaded architecture.
- Ensures seamless fallback to single-threaded mode when duo_chat_multi_thread is disabled.

EE: true

Add a drawer component to the vulnerability details page to display
dependency paths. Introduce the dependency_paths feature flag.

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

This resolves an issue where severity details
are not rendered on vulnerability details page

EE: true
Changelog: fixed

Rename index.md to _index.md and update crosslinks
from other docs and code files.

Changelog: changed

Don't use constants in tests, clean up severityOptions in modal

Submitting a severity change on the vulnerability details page
via the "Change severity" action in the "Edit vulnerability" dropdown
should call the mutation to update the severity of the vulnerability
and refresh the severity displayed on the page

Enhance severity_badge by adding an icon to indicate when severity changed and also include a tooltip

The security scores are now generally available and viewable on the
vulnerability report and single vulnerability page.

Changelog: other
EE: true

Keep constants in header.vue (only used there)
i18n-ify one more string
Make wrapper.emitted matching stricter
Add test for loading state of dropdown

When vulnerability_severity_override feature flag enabled,
show a dropdown with "Change status" and "Change severity"
Otherwise, show the existing "Change status" buttons

This removes the feature flag `vulnerability_details_state_modal`.
This makes the Vulnerability Change Status modal the default, which
allows you to add a comment (required for dismiss status).

The documentation is also updated to reflect the new user flow.

Changelog: added
EE: true

The security scores are displayed in the vulnerability report. This
commit brings that functionality to the vulnerability details page.

This commit removes the `vulnerability_representation_information` feature flag and deletes its configuration file.
- Updated related files and tests to reflect the removal.
- Ensured no unintended dependencies remain.

Changelog: changed
EE: true

This adds, behind the `vulnerability_details_state_modal` feature flag,
a modal based way of changing the state of a vulnerability on the
details page. It also makes the comment mandatory when dismissing.

This reverts merge request !178050

This commit removes the feature flag 'vulnerability_code_flow' as it is no longer needed.

Changelog: removed

Negative index is not
supported in VUE 3

EE: true

This makes sure the system notes in the vulnerability details
discussions section do not show the username.

Changelog: changed
EE: true

Uses the GlAlert component to show the warning
message that informs the user that using
"Resolve with AI" on a public
project might expose the given vulnerability.

This is to ensure consistency across the
application.

This commit updates the public-MR
docs link to the latest URL.