Run Catalog integration tests against REST Catalog impls

[rambleraptor]

Closes #2481

Rationale for this change

This allows users to run our test suite against their REST Catalog implementations.

Are these changes tested?

Test-only change

Are there any user-facing changes?

• Adds support for running catalog tests against REST Catalog implementations.

[jayceslesar]

I think under the contributing or dev or somewhere in the docs can we specify how a user would do this?

[rambleraptor]

@jayceslesar I added docs in contributing that explains how to use this.

[gabeiglio]

This is great! thanks for working on this! Im thinking for future next steps would be on thinking how we can allow for custom catalogs to ignore tests that are not supported by that catalog like for example catalogs that do not support views or multi-level namespaces, and so on.

We should somehow allow the users to selectively skip tests, like for example java CatalogTests

[kevinjqliu]

This is a really interesting idea. Thanks for adding it!

[rambleraptor]

@kevinjqliu @Fokko @gabeiglio rebased and comments addressed! Thanks a lot

[Fokko]

@rambleraptor Why do I still need to approve your runs? :D

[Fokko]

LGTM, thanks @rambleraptor 🙌

[rambleraptor]

@Fokko if there's a way for you to let me do CI runs, that would be awesome!

[Fokko]

@rambleraptor I was under the impression that it should run after a merge. Let me check with infra

[rambleraptor]

I've seen in past non-Apache OSS projects that automatic CI runs are limited to a specific set of people (typically committers, not always).

The idea behind that is that you don't want random malicious people sending PRs with Bitcoin mining scripts in them

[rambleraptor]

@Fokko regardless, I changed the fixture name which should enable the tests to work. I'll try getting my integration test setup in a better situation to avoid having to rely on CI so much

[kevinjqliu]

Thanks @rambleraptor for the PR and @gabeiglio @Fokko for the review!