Fixing the revert merge request with large setup test

What does this MR do?

This test only failed in the large setup pipeline for some reason. After looking into it, it was obvious that due to changes in the way the page loads when there are a lot of files present, it the selector could not be found.

After a closer look it seems that the selector on was updated to use a identifier since there are going to be as many selectors with that name as there are files, but instead of the identifier, it used the text to check. Since the page does not fully load when viewing large MRs, the text was never found.

After changing the page object to use the identifier, all issues where resolved.

E2E Test Failure issue(s)

• Needs to close the issue: #338324 (closed)
• OKR: gitlab-com/www-gitlab-com#12197 (closed)

Check-list

• General code guidelines check-list
  • Code review guidelines
  • Style guides
• Quarantine test check-list
  • Follow the Quarantining Tests guide.
  • Confirm the test has a quarantine: tag with the specified quarantine type.
  • Note if the test should be quarantined for a specific environment.
  • (Optionally) In case of an emergency (e.g. blocked deployments), consider adding labels to pick into auto-deploy (Pick into auto-deploy priority1 severity1).
• Dequarantine test check-list
  • Follow the Dequarantining Tests guide.
  • Confirm the test consistently passes on the target GitLab environment(s).
    • (Optionally) Trigger a manual GitLab-QA pipeline against a specific GitLab environment using the RELEASE variable from the package-and-qa job of the current merge request.
• To ensure a faster turnaround, ask in the #quality Slack channel for someone to review and merge the merge request, rather than assigning it directly.