Integration tests should cover both strong and eventual consistency domains

[kaikulimu]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

Our integration test suite allows us to test on either strong (SC) or eventual (non-SC) consistency domains based on domain name. Some of our tests use the SC domain, while others use the non-SC domain.

Expected Behavior

We should standardize such that all integration tests cover both strong and eventual consistency domains.

Steps To Reproduce

Look at the codebase and you will find many examples, e.g.)

1. test_admin_client.py tests on non-SC domain tc.DOMAIN_PRIORITY.
2. test_auto_subscriptions.py tests on SC domain tc.DOMAIN_PRIORITY_SC.

BlazingMQ Version

0.93.5

Anything else?

No response