[Spike] Investigate Skipped Stacks in Registry Nightly Run

[Jdubrick]

Which area/kind this issue is related to?

/area registry

Issue Description

We have a bunch of stacks that are currently being skipped during our nightly run tests on the Registry because they are not cooperating/failing. A list of these skipped stacks can be found here. Changes were made to the layout of the nightly run and the allocation of resources and this may have enabled certain skipped stacks to function properly.

For each stack the following needs to be done:

1. Test it against odov2 and odov3 to see if it passes
2. If it passes remove it from being skipped
3. If it fails open an issue for fixing the stack

Acceptance Criteria

• All skipped stacks tested
• Passing stacks are no longer skipped
• Failing stacks have issues opened for resolution

[Jdubrick]

Issue that would fall under this investigation opened here: #1533

[michael-valdron]

Issue that would fall under this investigation opened here: #1533

And #1514

[michael-valdron]

While testing for devfile/registry#366, I discovered why these checks might be currently failing. The odo v3 check reports that it fails on redhat-product starter project and when using it I get:

This starter project appears to be using /hello as the index endpoint to the odo dev deployment rather than root /, there will need to be an investigation into how to work around this for this starter project:

[thepetk]

Need to investigate the reason of this issue #1554 too.