[DEQUARANTINE] Create Changing Gitaly repository storage when moving from Gitaly to Gitaly Cluster behaves like repository storage move confirms a `finished` status after moving project repository storage

What does this MR do?

Dequarantines the test Create Changing Gitaly repository storage when moving from Gitaly to Gitaly Cluster behaves like repository storage move confirms a finished status after moving project repository storage (https://gitlab.com/gitlab-org/gitlab/-/blob/master/qa/qa/specs/features/api/3_create/gitaly/changing_repository_storage_spec.rb#L48)

This quarantined test has been found by Confiner to have passed 30 times consecutively, which exceeds the threshold of 10 times.

1. ce:praefect-quarantine
2. ee:praefect-quarantine
3. ce:praefect-quarantine
4. ee:praefect-quarantine
5. ce:praefect-quarantine
6. ee:praefect-quarantine
7. ce:praefect-quarantine
8. ee:praefect-quarantine
9. ce:praefect-quarantine
10. ee:praefect-quarantine
11. ce:praefect-quarantine
12. ee:praefect-quarantine
13. ce:praefect-quarantine
14. ee:praefect-quarantine
15. ce:praefect-quarantine
16. ee:praefect-quarantine
17. ce:praefect-quarantine
18. ee:praefect-quarantine
19. ce:praefect-quarantine
20. ee:praefect-quarantine
21. ce:praefect-quarantine
22. ee:praefect-quarantine
23. ce:praefect-quarantine
24. ee:praefect-quarantine
25. ce:praefect-quarantine
26. ee:praefect-quarantine
27. ce:praefect-quarantine
28. ee:praefect-quarantine
29. ce:praefect-quarantine
30. ee:praefect-quarantine

#284645 (closed)

(This MR was automatically generated by Confiner at 2022-03-26 01:21:05 UTC)

E2E Test Failure issue(s)

Running the test against EE:14.5.0, EE:14.6.0, EE:14.7.6, EE:14.8.0 reproduced the issue noted #348413 (comment 836865294)
With gitaly#4036 (closed) included in 14.9 this spec appears to be working again as expected.

Test Case: https://gitlab.com/gitlab-org/gitlab/-/quality/test_cases/347828
Failure Issue: #284645 (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.