feat!: support multiple ports in Proxyrack configuration

[rimiti]

Purpose

This pull request refactors the configuration for the Proxyrack provider to simplify and unify the proxy configuration, particularly around port handling. Instead of supporting both a single port and an array of ports depending on the strategy, the code now consistently uses an array of ports. This change streamlines the provider's interface and removes redundant type definitions.

Configuration unification and simplification:

• Replaced separate proxy config types for each strategy (TProxyrackProviderConfigStrategyChangeIpEveryRequest and TProxyrackProviderConfigStrategyManual) with a single TProxyrackProviderConfig type that always uses a ports array. The main config interface TProxyrackConfig now supports both strategies in a unified way. [1] [2]
• Updated the Proxyrack provider class to always select a port randomly from the ports array, regardless of the strategy, removing the previous conditional logic.

Code and documentation updates:

• Updated all usages and examples (including in README.md and tests) to use the ports array instead of a single port value. [1] [2]

[nodi-bot]

🎉 This PR is included in version 5.3.0 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀