Update SAST CI examples for leveraging existing build jobs

What does this MR do?

Per work on https://gitlab.com/gitlab-org/gitlab-ee/issues/8212, we should improve our SAST documentation to show custom execution strategies for projects which cannot take advantage of our default configuration. This improvements cover several important use cases:

1. Bypassing compilation during sast stage (for performance, security, or compatibility reasons)
2. Bypassing the requirement for Docker-in-Docker executions
3. Documenting the ability to upload/collate multiple job reports during a pipeline

What are the relevant issue numbers?

https://gitlab.com/gitlab-org/gitlab-ee/issues/8212

Does this MR meet the acceptance criteria?

• Changelog entry added, if necessary
• Documentation created/updated via this MR
• Documentation reviewed by technical writer or follow-up review issue created
• Tests added for this feature/bug
• Tested in all supported browsers
• Conforms to the code review guidelines
• Conforms to the merge request performance guidelines
• Conforms to the style guides
• Conforms to the database guides
• Link to e2e tests MR added if this MR has Requires e2e tests label. See the Test Planning Process.
• EE specific content should be in the top level /ee folder
• For a paid feature, have we considered GitLab.com plans, how it works for groups, and is there a design for promoting it to users who aren't on the correct plan?
• Security reports checked/validated by reviewer