Enable EventHub Management Node to use RequestResponseChannelCache

[anuchandy]

This is a follow up for #39107, in this PR weupdate the EventHub Management node to utilize RequestResponseChannelCache when V2 stack is opted-in as shown below –

final EventHubConsumerClient client = new EventHubClientBuilder()
        .connectionString(EH_CONNECTION_STRING)
        .consumerGroup("$Default")
        .configuration(new ConfigurationBuilder()
                .putProperty("com.azure.messaging.eventhubs.v2", "true")
                .build())
        .buildConsumerClient();

    // The API call that uses RequestResponseChannel obtained from RequestResponseChannelCache.
    client.getPartitionIds().forEach(partitionId -> {
        System.out.println(partitionId);
    });

If necessary, the new caches in v2 can be turned off by configuring 'com.azure.core.amqp.cache' to 'false'

[azure-sdk]

API change check

API changes are not detected in this pull request.

[joshfree]

If necessary, the new caches in v2 can be turned off by configuring 'com.azure.core.amqp.cache' to 'false'

Is there value in having a 'clearCachedData' API so that apps can flush the cache without restarting?

[joshfree]

Could you include a regression test case?

[lmolkova]

+1 to add a test-case

[anuchandy]

@joshfree

Is there value in having a 'clearCachedData' API so that apps can flush the cache without restarting?

We control it internally where cache gets cleared and refreshed automatically when cached channel gets disconnected like this and this

[anuchandy]

Could you include a regression test case?

This will be covered in the follow up pr (work item), that enables the existing "live tests" for v2 EH (like SB) then this path will get executed/exercised by the processor/management API test cases. (For the caches itself we have extensive "unit tests").