Now that the details are rendered explicitly, the markup had a lot of
duplication. This abstracts that duplication into a functional
component.

This refactors the new `vulnerability-details` component to explicitly
render the markup for the various details of the vulnerability, without
going through an unnecessary transformation stage.

This is preferable (though more verbose) because different details are
rendered in different ways. Before, the template resembled the
[loop-switch sequence][2] anti-pattern, and adding special cases was
awkward.

The snapshot changes in this commit are simply whitespace changes and
added/missing HTML comments, resulting from the different conditional
rendering logic.

This addresses [issue 32039][1].

[1]: https://gitlab.com/gitlab-org/gitlab/issues/32039
[2]: https://en.wikipedia.org/wiki/Loop-switch_sequence

This swaps out the component factory functions which rendered the old
`vulnerability-details` component, in each of the MR and Security
Dashboard contexts, with a new factory function that renders only the
new version of the component.

The snapshot changes in this commit correspond to the expected changes:

- the MR context now includes (if available):
  - the project the vulnerability belongs to
  - the report type of the vulnerability
  - the line number information for the `file`
- the Security Dashboard context now includes (if available):
  - the method in which the vulnerability was detected

This ports the existing tests for the old `vulnerability-details`
component to the new one, since it now accepts a `vulnerability` prop
rather than a `details` prop.

This duplicates the existing `vulnerability-details` component, and
replaces its `details` prop  with a `vulnerability` prop.

To achieve this, the data transformations which turned a `vulnerability`
object into a `details` object have been naively copied into this new
component.

The main data transformation is copied mostly verbatim from the
[SET_MODAL_DATA mutation][1] in the Security Dashboard store, rather
than from [SET_ISSUE_MODAL_DATA][2] mutation in the security reports
store in the Merge Request page. This is because the former is slightly
more complete than the latter:

- it includes the project the vulnerability belongs to
- it includes the report type of the vulnerability
- it includes line number information for the `file`, if it exists

The latter, however, includes the method in which the vulnerability was
detected, if it exists.

All this is to say that in addition to rendering everything the old
component did, the new component:

- in the MR context:
  - includes the project the vulnerability belongs to (if available)
  - includes the report type of the vulnerability (if available)
  - includes line number information for the `file` (if available)
- in the Security Dashboard context:
  - includes the method in which the vulnerability was detected (if
    available)

The [secondary transformation `valuedFields`][3] is copied almost
verbatim from the containing modal.

[1]: https://gitlab.com/gitlab-org/gitlab/blob/v12.8.1-ee/ee/app/assets/javascripts/security_dashboard/store/modules/vulnerabilities/mutations.js#L76-158
[2]: https://gitlab.com/gitlab-org/gitlab/blob/v12.8.1-ee/ee/app/assets/javascripts/vue_shared/security_reports/store/mutations.js#L135-172
[3]: https://gitlab.com/gitlab-org/gitlab/blob/v12.8.1-ee/ee/app/assets/javascripts/vue_shared/security_reports/components/modal.vue#L123-138

This adds snapshot tests for the `vulnerability-details` component as it
currently exists in the two main contexts it appears in:

- in Merge Requests
- any Security Dashboard

Snapshots for both contexts are created, because the data is processed
in slightly (though very similar) ways in each.

A relatively wide selection of real vulnerability findings is used in
both contexts to ensure good coverage.

The purpose is to establish a baseline to facilitate refactoring the
component, and the data paths in both contexts, without changing the
final rendered output.

Use available? method for Elastic Stack availability

See merge request gitlab-org/gitlab!25615

Fix flaky wiki specs by waiting for the SVG to be loaded first

Closes #27972, #27964, #27951, and #207817

See merge request gitlab-org/gitlab!25982

Add S3 warning to Package Docs

See merge request gitlab-org/gitlab!24729

Change boolean value

Separate ee entities into own class files

See merge request gitlab-org/gitlab!25709

Refactor import_export

Closes #207846

See merge request gitlab-org/gitlab!25623

Rename GitAccess::UnauthorizedError and align git returned error codes

See merge request gitlab-org/gitlab!25936

Replace set to let_it_be in spec/features

See merge request gitlab-org/gitlab!25889

Migrate the Gemfile Danger check to static-analysis instead

Closes #202299

See merge request gitlab-org/gitlab!25986

Fix displaying blocked issues on the board

See merge request gitlab-org/gitlab!25817

Get rids of set in spec/features

Quarantine a flaky test in spec/lib/gitlab/profiler_spec.rb

See merge request gitlab-org/gitlab!25993

Updates security MR template

See merge request gitlab-org/gitlab!25919

In this commit we rename GitAccess::UnauthorizedError
to ForbiddenError to align it with the kind of returned
error 403.

Besides we also fix the error code returned through
the internal api and align it to use 403 as well.

Fixes Vue file list for paths with non-ascii characters

Closes #207499

See merge request gitlab-org/gitlab!25877

Migrate gke_zone_dropdown_spec to Jest

See merge request gitlab-org/gitlab!25813

Migrated /gke_cluster/components/gke_zone_dropdown_spec.js file
to migrate tests from karma to jest.

Update file content of an existing custom dashboard

Closes #34525

See merge request gitlab-org/gitlab!25024

Add update route to dashboard controller

Add update action to dashboard controller

Start adding specs for UpdateDashboardService

Serve :bad_request when the file update fails

Add test for path traversal

Flesh out dashboard details and additional specs

Run static analysis

Fixing comment

Use Label#scoped_label_key when determining scope

See merge request gitlab-org/gitlab!25952

Return 503 to Runner when object storage is unavailable

See merge request gitlab-org/gitlab!25822

Enforce max daterange on VSA

See merge request gitlab-org/gitlab!25678

Keep the needs association on the retried jobs

See merge request gitlab-org/gitlab!25888

Change needs in CLONE_ACCESSORS to needs_attributes
because it was reassigning the needs relationship
to the new build.

- Move files to Project/* namespace
- Move files to Group/* namespace
- Fix specs

Signed-off-by: Rémy Coutable <remy@rymai.me>

Quarantine flaky karma tests

See merge request gitlab-org/gitlab!25983

Related to https://gitlab.com/gitlab-org/gitlab/issues/206907.
Signed-off-by: Rémy Coutable <remy@rymai.me>

Apply license to selected group

Closes #207970

See merge request gitlab-org/gitlab!25895

Catch object storage errors and return 503 to the
Runner for artifacts uploads.

Fix weight not showing in linked issues

See merge request gitlab-org/gitlab!25718