chore: remove usage of deprecated connection methods in command APIs in integration tests (#3328)

[The-East-Wind]

Make sure that:

• You have read the contribution guidelines.
• You have created a feature request first to discuss your contribution intent. Please reference the feature request ticket number in the pull request.
• You applied code formatting rules using the mvn formatter:format target. Don’t submit any formatting related changes.
• You submit test cases (unit or integration tests) that back your changes.

Part of #3328

Changes

• remove usage of deprecated flushCommands, isOpen, setAutoFlushCommands and close in integration tests and changed to use alternate methods from StatefulRedisConnection and StatefulRedisClusterConnection.
• remove usage of deprecated isOpen in set client name flow for cluster commands
• remove some usages of deprecated getStatefulConnection from integration tests
• remove deprecated flushCommands, isOpen, setAutoFlushCommands and close methods from command APIs

Follow up

• getStatefulConnection is still being used in > 50 integration tests, this is to be removed before the method can be removed from the command APIs

[tishun]

Hey @The-East-Wind , which of the tasks in #3328 does this PR address?

[The-East-Wind]

@tishun This aims to partially address follow up to https://github.com/redis/lettuce/issues/2028 clean up the connection-related APIs, e.g. BaseRedisCommands. If the approach I've taken is acceptable I'll follow the same and complete it.

[tishun]

Hey @The-East-Wind ,

yes, I think this is the correct approach. Do you have something specific that you are concerned about?

[The-East-Wind]

@tishun the number of places which required change was high so I wanted to confirm I was following the right approach before make all the changes so that there is no rework. I was specifically concerned about using try-with-resource for closing connections instead of explicitly calling close as throughout the tests explicit close calls were used instead of try-with-resource.

[tishun]

@tishun the number of places which required change was high so I wanted to confirm I was following the right approach before make all the changes so that there is no rework. I was specifically concerned about using try-with-resource for closing connections instead of explicitly calling close as throughout the tests explicit close calls were used instead of try-with-resource.

Sorry, saw your comment just now. What you did was great work, thanks a bunch!

try-with-resources could be used anywhere, my speculation is that it was not used because the codebase is old and there were times when it was not available as a construct.