[tests-only] Version metadata API acceptance test

[phil-davis]

Description

This is the rebased code from PR #39478 with an extra commit to get the test scenario passing.

I have added commented steps in the test scenario to indicate what I think the actual behavior should be.

The actual steps demonstrate the existing behavior, which is not correct.

This is part of issue #39504

This is a test that should be made to pass in #39516 - which is intended to fix the issue. That will likely be fixed in release-10.9.0 branch. So we can't merge this test PR.

How Has This Been Tested?

CI and local run of the new test scenario

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Database schema changes (next release will require increase of minor version instead of patch)
• Breaking change (fix or feature that would cause existing functionality to change)
• Technical debt
• Tests only (no source changes)

Checklist:

• Code changes
• Unit tests added
• Acceptance tests added
• Documentation ticket raised:
• Changelog item, see TEMPLATE

[sonarqubecloud]

Kudos, SonarCloud Quality Gate passed!   

0 Bugs
0 Vulnerabilities
0 Security Hotspots
0 Code Smells

No Coverage information
No Duplication information

[phil-davis]

This is a test that should be made to pass in #39516 - which is intended to fix the issue. That will likely be fixed in release-10.9.0 branch. So we can't merge this test PR.

[phil-davis]

PR #39516 has been merged into release-10.9.0 and is part of 10.9.0-RC1. The test is in that.

This draft is no longer needed - closing.