Tracked in https://gitlab.com/gitlab-org/gitlab-ee/issues/13496.

Clean up issues that may cause the docs-lint
test to fail, such as trailing whitespace, no
EOF newline, blockquotes, etc

Updated container scanning docs with a sample config

Includes admin_area and application_security
topics.

The manual job definitions are deprecated and are not
guaranteed to work as expected. We should not confuse
our users with including them in the docs.

This deletes all the deprecated sections and cleans up
the configuration section significantly.

Previously, we used brackets to denote the tier badges,
but this made Kramdown, the docs site Markdown renderer,
show many warnings when building the site. This is now
fixed by using parentheses instead of square brackets.

This was caused by [PREMIUM] looking like a link to
Kramdown, which couldn't find a URL there.

See:
- https://gitlab.com/gitlab-com/gitlab-docs/merge_requests/484
- https://gitlab.com/gitlab-org/gitlab-ce/issues/63800

Addresses the following questions:

- How often do we update the vulnerability DB or analyzers?
- Do we have to update GitLab to benefit from latest vulnerabilities
  definitions?