Document all the available options for Container Scanning

Problem to solve

Our Container Scanning tool supports options to tweak its behavior.

The documentation needs to be organized to provide a single point of contact where everything is clearly accessible.

Current documentation https://gitlab.com/gitlab-org/security-products/container-scanning

Proposal

We need to improve our documentation and provide any supported option (normally via environment variable).

If we have "experimental" options that are not supported, we should document them as well, with a clear statement that they are experimental/unsupported, and may change in the future. This will allow customers to be aware of the case and to take proper actions.

Who can address the issue

• PM
  • Prioritize doc changes as part of &866 (closed)
• Developers
  • check and provide the matrix of supported options.
  • test that those options are working (first iteration)
  • set up automated tests to constantly check those options (second iteration)
• UX
  • Check that user journeys are going flawless from problem to solution, through documentation
• Tech Writers
  • Help in organizing info so that users can find them and consume easily