Do not use hard-coded path in tests

What does this MR do and why?

In order to avoid flaky tests, do not use hard-coded paths in tests, but rather use project.full_path. This fixes master:broken incident - gitlab-org/quality/engineering-productivity/master-broken-incidents#3635 (closed). The MR that introduced the hard-coded paths is !131068 (merged).

Screenshots or screen recordings

Screenshots are required for UI changes, and strongly recommended for all other merge requests.

Before	After

How to set up and validate locally

Numbered steps to set up and validate the change are strongly suggested.

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.