Adds a wait to make sure test is on the correct merge request

What does this MR do and why?

The merge request pipeline appears to be generated slower and the test is ending up on the branch pipeline instead which is why it is failing as the branch pipeline will show the non_mr_only_job as that branch pipeline is not a merge request pipeline. This change introduces a wait that will make sure that it is on the correct pipeline first before proceeding with the expects

Related to #379036 (closed)

MR acceptance checklist

This checklist encourages us to confirm any changes have been analyzed to reduce risks in quality, performance, reliability, security, and maintainability.

• I have evaluated the MR acceptance checklist for this MR.