[resource manager] Refactor resourcemanager tests to work with latest TestProxy

[samvaity]

[resource manager] Refactor resourcemanager tests to work with latest TestProxy

[scbedd]

Tag me in @weidongxu-microsoft with questions. I have reason to believe that something in the upstream sanitizers is messing with the batching of azure-core on java side, so requests aren't flowing as quickly as they should be.

We saw that with .NET, due to the sanitizer AZSDK3448

[weidongxu-microsoft]

resourcemanager sanitizer mostly here
https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/resourcemanager/azure-resourcemanager-test/src/main/java/com/azure/resourcemanager/test/ResourceManagerTestProxyTestBase.java#L439-L480

a few module would add a few more, e.g.
https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/resourcemanager/azure-resourcemanager-containerregistry/src/test/java/com/azure/resourcemanager/containerregistry/RegistryTest.java#L28-L33

[weidongxu-microsoft]

We are actually fine with @liveOnly.

If we upgrade api-version of a service, we generally require dev to re-run them as LIVE or RECORD, as there is no promise that backend does not have behavior change (that can only be figured out when run LIVE).
If SDK dev can catch the behavior change, SDK customer may not get impacted, or at least get a warning in changelog.