Thanks @rambleraptor, this is a cool idea, took me a bit to think this one through. Polaris moves fast, and having it in CI means we automatically validate against a robust REST catalog implementation not waiting on rck changes. I'm looking forward to this being the foundation for testing scan planning and vended credentials once that path is finalized.

Right now this adds the full e2e workflow to run the basic catalog tests against Polaris, which is a good start that we can stand up Polaris and run against it even outside of testing. I also wanted to call out that there is a lot of value in Polaris on other fronts like credential vending, access, auth flows. Is there a plan to expand the test surface toward that?

Also, left a few comments on a first pass, and will leave open for some other comments!