Split acceptance tests into Basic and Advanced Acceptance test classe…

…s for readability. (airbytehq#13508)

Refactor the acceptance tests for readability & speed by splitting acceptance tests into a basic and advanced test class.

- Basic test class: Contains all tests around functionality that stays constant regardless of deployment. e.g. api changes. Only run for Docker.
- Advanced test class: Contains all tests around functionality that changes due to deployment. e.g. how we handle processes between Docker and Kubernetes. Runs for both Docker and Kubernetes.

The benefits are:
- Breaks up the huge monolith tests we have today for better readability. Preps us to run these tests on Cloud.
- Clarifies what tests run on what deployment.
- Gradle parallelises at the level of the test class, so we get some speed up. Anecdotally, this is faster by ~3 mins over the old Kubernetes acceptance tests.

There is some test fixture duplication, but I figured we can tackle that in a follow up PR.