Feature: Smart Rotators & Robust Library Management

[thewebscraping]

This pull request introduces two major enhancements that significantly improve the library's anti-detection capabilities and overall robustness:

1. A Smart Rotator System: For automatically rotating proxies, headers, and TLS identifiers to effectively mimic authentic traffic.
2. Robust Library Management: A dependency-free, self-managing mechanism for handling the lifecycle of the core tls-client C library.

Detailed Changes:

1. The Rotator System

• Introduced Three New Rotator Classes: ProxyRotator, HeaderRotator, and TLSIdentifierRotator. These classes provide a unified sync/async API (next/anext methods) for managing and cycling through resources.
• Seamless Client Integration:
  • Smart Defaults: The Client and AsyncClient now enable header and TLS identifier rotation by default, using a curated set of built-in, realistic templates.
  • Unified Parameters: The proxy, headers, and client_identifier parameters now accept multiple types: a single value (for static use), a list (to automatically enable rotation), or a pre-configured Rotator instance.
  • Proxy Feedback Loop: The Client now automatically calls mark_result/amark_result on the ProxyRotator, providing performance feedback (success/failure, latency) to optimize the weighted rotation strategy.

2. TLSLibrary Refactor

• Dependency Elimination: The requests and tqdm dependencies have been completely removed. Library downloading now uses Python's built-in urllib and json modules, making the library lighter and more portable.
• Intelligent Version Management:
  • The TLSLibrary class is now version-aware. It compares the version of the local C library file against a required version constant (LATEST_VERSION_TAG_NAME) hardcoded in the package.
  • Automatic Upgrade/Installation: If no local library is found, or if the existing version is outdated, TLSLibrary.load() will automatically download the correct version from GitHub.
  • Automatic Cleanup: After a successful download or validation of a new version, old library files in the bin directory are automatically deleted to prevent conflicts and keep the directory clean.

These changes transform the library from a powerful tool into a more intelligent, self-managing, and reliable solution for automation and scraping tasks.