improvement(compat testing): Automatically load a second container when running cross-client compat e2e tests

[scottn12]

This is a WIP and is not yet intended to be merged

Description

This PR ensures that a second container is always loaded when running cross-client compat tests. Additionally, it adds skipSecondContainerLoad to ITestContainerConfig which allows tests authors to disable this functionality.
This PR leverages skipSecondContainerLoad in 4 test suites. Without that option, those test suites would fail since they were written with the assumption that only a single contianer would be loaded.

Test Runtime Increase

On a codespaces instance, I ran time pnpm test from the test-end-to-end-tests package three times with and without the changes in this PR.

With second container
Run 1: 13m3.357s
Run 2: 14m18.576s
Run 3: 12m44.915s

Without
Run 1: 12m38.526s
Run 2: 12m23.861s
Run 3: 12m41.466s

We would need to re-test for more accurate/consistent results, but we can expect a small, but noticeable, increase in runtime.

Misc

AB#6826