Description of change

This PR adds a DriverInfo class to enable upstream drivers (like django-redis, celery, rq, etc.) to identify themselves when using redis-py as their underlying client.

Key features:

• DriverInfo dataclass that tracks upstream driver name and version
• Formatted output follows the pattern: redis-py(driver1_vVersion1;driver2_vVersion2)
• Validation ensures driver names follow Python package naming conventions (lowercase, start with letter, only letters/digits/hyphens/underscores)
• Validation ensures driver versions contain only printable ASCII without spaces or braces
• Integration with both Redis and AsyncRedis clients via optional driver_info parameter
• Pool propagation: driver_info is automatically propagated from client to connection pool to individual connections
• Deprecation: lib_name and lib_version parameters are now deprecated in favor of driver_info
• Fallback behavior: if driver_info is not provided, it's created from lib_name/lib_version (if present)
• Most recently added driver appears first in the formatted name

Example usage:

from redis import Redis, DriverInfo

# Create DriverInfo with upstream driver
info = DriverInfo().add_upstream_driver("django-redis", "5.4.0")
client = Redis(driver_info=info)
# Client will identify as: redis-py(django-redis_v5.4.0)

# Legacy parameters (deprecated)
client = Redis(lib_name="django-redis", lib_version="5.4.0")  # Still works but shows deprecation warning

Pull Request check-list

• Do tests and lints pass with this change?
  • All 17 tests passing (11 DriverInfo tests + 6 client setinfo tests)
  • ruff check passes
  • ruff format --check passes
• Do the CI tests pass with this change (enable it first in your forked repo and wait for the github action build to finish)?
  • Will enable and monitor
• Is the new or changed code fully tested?
  • Comprehensive test suite covering:
    • Default behavior (no upstream drivers)
    • Single upstream driver
    • Multiple upstream drivers (latest first)
    • Invalid driver name validation (4 test cases)
    • Invalid driver version validation (3 test cases)
    • Client setinfo with driver_info parameter (sync and async)
    • Pool propagation (async with single connection and pool)
    • Deprecation warnings for lib_name/lib_version
• Is a documentation update included (if this change modifies existing APIs, or introduces new ones)?
  • Docstrings added to all public methods and classes
  • Examples included in docstrings
  • Deprecation notices added to lib_name and lib_version parameters
• Is there an example added to the examples folder (if applicable)?
  • Not applicable - this is a utility class for library integrators, not end users