Allow passing in the connection_pool_class to the Client

[cancan101]

Pull Request check-list

Please make sure to review and check all of these items:

• Does $ tox pass with this change (including linting)?
• Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
• Is the new or changed code fully tested?
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
• Is there an example added to the examples folder (if applicable)?
• Was the change added to CHANGES file?

NOTE: these things are not required to open a PR and can be done
afterwards / while the PR is open.

Description of change

Please provide a description of the change here.

[codecov-commenter]

Codecov Report

Patch coverage: 100.00% and project coverage change: -0.05 ⚠️

Comparison is base (6c708c2) 92.31% compared to head (23af240) 92.27%.

📣 This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #2618      +/-   ##
==========================================
- Coverage   92.31%   92.27%   -0.05%     
==========================================
  Files         115      115              
  Lines       29744    29744              
==========================================
- Hits        27459    27446      -13     
- Misses       2285     2298      +13     

Impacted Files	Coverage Δ
redis/asyncio/client.py	93.27% <100.00%> (ø)

... and 5 files with indirect coverage changes

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[cancan101]

An additional advantage of passing the connection_pool_class to the Client rather than the connection_pool itself is that allows for the Client to have auto_close_connection_pool be True. I don't know all the implications of this but it looks like auto_close_connection_pool will always be false if a pool is provided.

[mohd-akram]

What's the status of this?