Trying to allow time for component to become available
What does this MR do and why?
Attempting to fix https://gitlab.com/gitlab-org/gitlab/-/issues/452553
I couldn't reproduce this locally so I suspected that we didn't allow enough time for the component to become available before calling it in the test project CI.
- There isn't a way to quickly/directly verify if the component is available, so I added a check to make sure the release is available.
- Also not waiting for pipeline to pass on Pipelines page since I realized we don't have much information to go on from the screenshot. If we go to Pipeline details page instead and it fails we can see the reason why.
- Not related to the failure but I was able to confirm that when a project is permanently deleted, the component will be removed as well. So this should be taken care of in our test resources delete jobs. I'm removing the
:skip_live_env
tag here so these tests can run in dotcoms.
Related to #452553
Edited by Tiffany Rea