Potential e2e test gap with the clone panel feature
<!--IssueSummary start-->
<details>
<summary>
Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards.
</summary>
- [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=378215)
</details>
<!--IssueSummary end-->
[We recently had a broken `master`](https://gitlab.com/gitlab-org/gitlab/-/issues/378203) where [the `.clone-options-dropdown` class was removed from a view file](https://gitlab.com/gitlab-org/gitlab/-/merge_requests/96923/diffs#ae8ea83306997a17af7e5b1ad379be93e83f52fb_13_12), but it was expected to be there by https://gitlab.com/gitlab-org/gitlab/-/blob/7a0d191291157d1eeabcda052156a6e3de55567e/app/assets/javascripts/clone_panel.js#L4.
The ~"pipeline:run-full-rspec" label was removed from the MR, so that only "minimal" jobs ran, and since we don't have `view file` -> `test` mapping, the "minimal" jobs didn't run the relevant spec files, so the MR was merged with a green pipeline.
Another problem was that no e2e tests (either in Review Apps or in `e2e:package-and-test`) failed!
We might want to investigate if we want to close this test gap at the e2e level.
issue