Cross-DC tests restart containers after every tests because the expected initial state is that exactly the first server node in first DC is started (and no other).
Introduce class- and method-level @InitialDcState annotation with attributes authServers and cacheServers, each taking at least these values and update starting servers accordingly:
The servers (managed by testsuite) would be started and stopped before a test to prepare the environment accordingly. It would be possible to override class-level default in individual methods.
Note that for cache servers, in the current setup with a single cache server the FIRST_NODE_IN_EVERY_DC would be the same as ALL_NODES_IN_EVERY_DC