GitLab Next

Ensure manual pages have link to Auto DevOps page.

We should talk about CI/CD variables, not environment
variables, when talking about variables used in CI/CD

Take care of more spelling issues: edit the words, put them in code
tags, or add them to the spelling exceptions list.

These pages in the Protect docset used the possessive form of
GitLab, which isn't OK from a legal perspective.

Minor updates to protect content to remove future tense & possessives.

In &5020, we decided to
use only two alerts (note, warning), and eliminate any bold text
coming after the icon.

This changes CAUTION to WARNING and eliminates any
**Warning:**/**Caution:** text that comes after them.

The previous URL had two drawbacks:

1. It didn't match what the title was about (`Assignments to DevOps
   Stages and Groups`, and the anchor was `#designated-technical-writers`).
2. It didn't account for the other sections, like development and API
   guidelines.

Update requirements with link to supported distributions

There are some ways to format script sections
to change how they display in job logs. These
should be documented separately, to allow for
more detailed examples (covering different OSes,
for example). We also need to split the before_script
and after_script details, as they work differently.

Some runner features can be configured with variables,
but these details should be in the runner docs, not
the CI YAML ref.

docs: Add changelog entry
docs: add documentation on CS_MAJOR_VERSION
docs: add example of how to use older version

Update doc/user/application_security/img/vulnerability_page_download_patch_button_v13_1.png, doc/user/application_security/img/vulnerability_page_merge_request_button_v13_1.png, doc/user/application_security/img/vulnerability_page_merge_request_button_dropdown_v13_1.png files

Related to: #247950

Support is seeing many tickets about these errors and warnings.
This adds basic advice about where to find more specific messages
and how to enable logging to find even more details.

The idea behind updating both `application_security/index.md` and
`job_artifacts.md` with almost similar advice is that the latter
is probably the "last resort".

More details and review discussion:
!42486

Fixes: #202553

Related to: #233529

* Remove starter-only
* Remove core-only
* Remove premium-only
* Remove ultimate-only
* Remove ultimate
* Remove premium
* Remove starter
* Remove core

This adds bold and severity-specific colour styling to the numbers of
critical and high severity vulnerabilities in the security-related merge
request widgets.

Addresses #221084.

Also updates documentation

- Takes into account severities
- a11y compatible
- Updates all the helpers that go along with it
- Updates the documentation
- Updates all the tests that rely on this function.

- Updates version on Build, Code Quality and performance jobs
- Updates docs.

- This MR adds metadata to several of the Secure group's
  documentation files. The metadata is intended to guide
  Support and others to the relevant writer.