Update dependency scanning QA template for new CI/CD component

Why are we doing this work

In Create Dependency Scanning CI/CD Component (#433267 - closed) • Oscar Tovar • 17.5 • At risk, we created a CI/CD component for the new dependency scanning analyzer that was developed as part of Full dependency graph support in new component ... (&7288 - closed) • Igor Frenkel. It would be good to trigger scans for our test projects on analyzer release or component update, and ensure the following:

• job(s) pass successfully
• artifacts are generated correctly

The current QA script lives in the ci-templates project. Since we'll maintaining Gemnasium with critical updates for some time, it may be necessary to add a separate script that tests the new component + analyzer.

Implementation plan

Plan 1

• Use the existing qa testing to add support for remaining package managers

Plan 2

• Dynamically include the dependency scanning component when running qa
• Use the analyzer release to get list of package managers to be tested
• Create one test run per package manager

Verification steps

/cc @willmeek