Configure container scanning CI to trigger blocking bridge jobs for test projects
Background
In order to properly test and QA our analyzers and their wrapper ~Secure projects we should setup multi-project pipelines to trigger downstream executions of our test projects from analyzer projects. We currently rely on either manual testing or analyzers' included test/fixtures to ensure there are no regressions. This is time consuming and not very efficient.
Issue
We recently introduced new jobs to CI templates in order to trigger test project's pipelines. We done configuring those for DS analyzers. You can see how it is done in DS here or you can simply check gemnasium-python. We should adapt similar configuration for Container Scanning. Here are the test projects using container scanning: https://gitlab.com/explore/projects?tag=Container+Scanning