[v0] Update CI: build, test, tag, release images

What does this MR do?

Back-port to v0 the new CI configuration of master (Dependency Scanning v2) introduced in !43 (merged).

The pipeline proceeds in 3-6 stages:

• test and lint the Ruby project
• build a temporary image
• test and scan the image
• test against test projects ("downstream" pipelines) if QA jobs are defined
• tag the image
• release for GitLab

QA jobs (test projects)

• java-maven
• js-npm
• js-yarn
• php-composer
• python-pip
• ruby-bundler

What are the relevant issue numbers?

This is needed to prevent regressions on doing the back-port described in gitlab-org/gitlab#33321 (closed)

Does this MR meet the acceptance criteria?

• [-] Changelog entry added
• [-] Documentation created/updated for GitLab EE, if necessary
• [-] Documentation created/updated for this project, if necessary
• [-] Documentation reviewed by technical writer or follow-up review issue created
• Tests added for this feature/bug
• [-] Job definition updated, if necessary
• [-] Conforms to the code review guidelines
• [-] Conforms to the Go guidelines
• [-] Security reports checked/validated by reviewer