Use non-DinD setup for Dependency Scanning QA

Summary

Since #36526 (closed) there are regression tests ensuring that analyzer projects properly work with the non-DinD setup (that is, without the Docker-in-Docker orchestrator). With non-DinD becoming the default, the non-DinD setup should be tested in the pipeline of the analyzer projects when pushing new commits, and not on a daily basis, in scheduled pipelines of the test projects.

Improvements

Update the CI configuration of the Dependency Scanning analyzer projects so that QA uses the no_dind-FREEZE branches of the test projects.

Risks

Broken build

Involved components

• analyzer projects: gemnasium, gemnasium-python, gemnasium-maven, retire.js, and bundler-audit
• test projects

Optional: Intended side effects

QA jobs will only check the output of the analyzer project that is built in the pipeline, and not the output of other analyzer projects compatible with the same test projects.

Optional: Missing test coverage

None.