Check health of containers in e2e tests

[emmatyping]

We want to check that all the containers are healthy after we run the event through the test instance - this catches any containers that crash due to an issue at runtime.

Currently we only check container health in the installer.

[BYK]

Did this actually happen causing a bug getting through? If so I'm willing to submit a PR :)

[emmatyping]

Yes, just before the 22.10.0 release, the error and transaction pipelines were split, causing getsentry/sentry#40120

If you would like to submit a PR to add this that would be great, but I think if we are going to centralize our e2e tests (#1756 for anyone reading along) we should probably hold off until that is done first.