chore: disable flaky test that fails with ExitFailure (-9)

[cgrindel]

Per this conversation, to prevent out-of-memory (OOM) errors, we will shut down Bazel servers started by RunTests.hs. Unfortunately, we still see occasional Exit Code: ExitFailure (-9) errors. Printing the memory/process information in CI will provide additional details when/if it occurs, again.

• Refactor RunTests.hs so that tests for each workspace live under a separate describe.
• Add afterAll_ hook to shutdown Bazel after all of the tests for a workspace.
• Add around_ hook to print memory/process information before and after each test. This is enabled by setting the environment variable RHT_PRINT_MEMORY to true.
• For now, disable the flaky test.

Related to #2089.

[avdv]

Just a minor comment, otherwise LGTM.

[cgrindel]

@avdv For now, I recommend that we disable the test that exhibits the error. I will continue my investigation. However, these errors are hindering other work items. Hence, I am asking for another code review.