Add keep_alive and max_connections configuration to IncogniaAPI

[alangalvino]

PR body:

Summary

• Add keep_alive (bool) and max_connections (int) parameters to IncogniaAPI
• When keep_alive=True, a requests.Session is created with an HTTPAdapter configured with pool_connections and pool_maxsize set to max_connections
• The session is shared between the API client and TokenManager so all requests (including token refresh) benefit from connection reuse
• Defaults to keep_alive=False (existing behavior) and max_connections=10

[Copilot]

Pull request overview

Adds optional HTTP connection reuse to the Python client by introducing keep_alive and max_connections configuration and wiring a shared requests.Session through both the API client and token refresh path.

Changes:

• Add keep_alive/max_connections parameters to IncogniaAPI and BaseRequest, enabling a pooled requests.Session when configured.
• Allow TokenManager to accept an injected BaseRequest so token refresh uses the same connection pool.
• Add tests and README documentation describing the new configuration.

Reviewed changes

Copilot reviewed 5 out of 5 changed files in this pull request and generated 4 comments.

Show a summary per file

File	Description
incognia/base_request.py	Creates and uses a pooled requests.Session via HTTPAdapter when keep_alive=True.
incognia/api.py	Exposes keep_alive/max_connections on IncogniaAPI and shares the request instance with TokenManager.
incognia/token_manager.py	Supports dependency injection of BaseRequest so auth requests reuse the same session.
tests/test_base_request.py	Adds unit tests for the keep-alive/session behavior.
README.md	Documents the new keep-alive configuration and shows an example.

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.