Document DAST JSON report format

Problem to solve

Currently, our DAST tool generates the scanning report in ZAProxy format which is not compliant with our common library report format. Soon, this will be changed (see item 3. Make the DAST wrapper generating a report following the common format. ... of our architecture migration epic for DAST).

Afterwards, the report format must be documented for our customers and wider community. It should be done in a similar fashion of what has already been implemented for SAST and Dependency Scanning.

Further details

Also, the inclusion of scanned URLs list to the report is a prerequisite for this documentation effort.

Proposal

Document the . It should be done in a similar fashion of what has already been implemented for SAST and Dependency Scanning.

Depends on

This issue depends on, #14053 (closed).