feat: add pool_maxsize parameter to connection managers

[andrewmooreio]

Description

This PR adds a pool_maxsize parameter to the KeycloakOpenID and KeycloakAdmin classes. This parameter is passed to the internal ConnectionManager, allowing users to configure the maximum number of connections to keep in the connection pool.

Motivation/Context

Controlling the connection pool size is important for managing resource usage and improving performance in applications that make frequent calls to Keycloak. By exposing this parameter, users of the library can fine-tune the connection behaviour to better suit their environment and workload, potentially reducing overhead from establishing new connections.

Should resolve: #630

Testing Evidence

• Added pool_maxsize parameter to relevant test fixtures in tests/conftest.py with a non-default value (5).
• Added assertions in tests/test_keycloak_openid.py (test_keycloak_openid_init and test_a_well_known) to verify pool_maxsize is correctly set on the ConnectionManager for KeycloakOpenID.
• Added assertions in tests/test_keycloak_admin.py (test_keycloak_admin_init and test_a_realms) to verify pool_maxsize is correctly set on the ConnectionManager for KeycloakAdmin.

[andrewmooreio]

Note, the failed tests seem to be unrelated to this change and have been failing in CI for a while.

[ryshoooo]

Hi @andrewmooreio

Thanks a lot for the changes! Overall looks good to me, I can't spot anything breaking. I've only added a comment about the tests, ideally we want to keep the fixtures as simple as possible, there is no need to set the pool size for each fixture.

[ryshoooo]

Can we keep the fixtures minimal and just delete the pool_maxsize in here? (i.e. let the defaults take place). This way we can be sure that minimal configuration will keep working for most operations.

[ryshoooo]

Similar here. There's no need to set the pool max size for all these cases. 1 time is enough.