Refactor test to use a dynamic value for expectation

What does this MR do?

While looking into setting up project for UX research Control scope for CI/CD variables I discovered this spec has been producing false positive expectation 😓 Updating:

• Reduce setup scopes to use group level runner instead of 2 project level runners
• Update after block to remove runner and group afterward
• Update test to expect a dynamic variable value in downstream job.

Does this MR meet the acceptance criteria?

Conformity

• [-] I have included a changelog entry, or it's not needed. (Does this MR need a changelog?)
• [-] I have added/updated documentation, or it's not needed. (Is documentation required?)
• [-] I have properly separated EE content from FOSS, or this MR is FOSS only. (Where should EE code go?)
• [-] I have added information for database reviewers in the MR description, or it's not needed. (Does this MR have database related changes?)
• I have self-reviewed this MR per code review guidelines.
• This MR does not harm performance, or I have asked a reviewer to help assess the performance impact. (Merge request performance guidelines)
• I have followed the style guides.