Propage ENV variables to codequality

Ref: #11100 (closed)

What does this MR do?

This MR makes it possible to override our codequality ENV variables.

It includes the following items:

• Extract propagate_env_vars to lib/gitlab/ci/templates/utils/env.sh
• Use it in our codequality template

Why are we doing this?

This approach is similar to what we are already doing for our dependency scanning template.

Here an example of how to use it after merging this MR:

variables:
 TIMEOUT_SECONDS: 1

include:
  - Code-Quality.gitlab-ci.yml

By extracting propagate_env_vars to utils.sh this will allow us to reuse this function in our other templates.

We will follow up and update those templates in a different MR.

Screenshot

Here our pipeline using this new configuration:

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