Improve SAST documentation for custom analyzers
Problem to solve
We should improve the documentation around implementing custom analyzers for SAST.
It is not clear what the requirements are for the output report of the analyzer so that the report can be utilized by the security dashboards. There will likely be a lot of overlap with Document third party integration for Security Reports, so that should be taken in to consideration when working this.
Also, we are moving away from Docker-in-Docker, so we should consider removing this section at that time, or improving this documentation to also support pipelines that have Docker-in-Docker turned off.