Move away from docker-in-docker for SAST

What does this MR do?

In support of Use non-DinD mode by default for Security Products, we want to DogFood DinD-less SAST.

Of note, the sast job has been intermittently failing and passing prior to this change. With this change, the sast job is split into several *-sast jobs and the nodejs-scan-sast job will fail every time. I have created a follow-up issue to address that.

Related Issue

Disable docker-in-docker for SAST

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team

Closes #32260 (closed).