bk: framework to override DRA version with files

[v1v]

What does this PR do?

Use files to override the DRA version used by the ITs

Why is it important?

Help with centralising what versions need to be used when the DRA does not produce those artifacts and help with the existing CODEOWNERS model, so robots-ci team don't need to be in the process of the review. See this thread for more context.

Checklist

• I have read and understood the pull request guidelines of this project.
• My code follows the style guidelines of this project
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have made corresponding change to the default configuration files
• I have added tests that prove my fix is effective or that my feature works
• I have added an entry in ./changelog/fragments using the changelog tool
• I have added an integration test or an E2E test

Disruptive User Impact

How to test this PR locally

Related issues

Questions to ask yourself

• How are we going to support this in production?
• How are we going to measure its adoption?
• How are we going to debug this?
• What are the metrics I should take care of?
• ...

[elasticmachine]

💔 Build Failed

• Buildkite Build
• Commit: e6b4ad8

Failed CI Steps

• fips:x86_64:sudo-true:fleet
• fips:x86_64:sudo-true:fleet
• fips:arm64:sudo-true:fleet

History

• 💛 Build #24177 was flaky 331373c

cc @v1v

[elastic-sonarqube]

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
No data about Duplication

See analysis details on SonarQube