WIP: Expose secrets configured for a job to Runner

Closed in favor of bunch of smaller MRs, starting with !34480 (merged).

What does this MR do?

This builds on top of !33014 (merged) and expose secrets configuration when present to the runners (if runner supports this feature).

This new ci_secrets_management feature is available for GitLab Premium and above tiers.

At the moment the feature is hidden behind feature flag named ci_secrets_management_vault.

Related to #28321 (closed) and #218746 (closed).

Screenshots

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