We waste resources by depending on a cambpm container for our Zeebe integration tests. We theoretically shouldn't have to rely on such a container as the Zeebe import is indepenednt of the engine. However, actually getting to this point of being able to remove the dependency will require a restructure of our test classes and maybe even could be tackled when we split ITs to be run with Optimize running in a "proper" cloud mode

ATs:

• When Zeebe import tests run, we don't depend on a cambpm container