Add proxy for each modules

[Maxou56800]

Problem

The project connects to multiple APIs:

• public APIs
• internal APIs (enterprise network)

A proxy feature already exists, but it is currently applied globally to all API calls.
In some environments (corporate networks, isolated environments, no direct Internet access), this approach lacks flexibility.

Current Limitations

• No way to define which module or API client uses which proxy
• Difficult to properly handle:
  • APIs that are only accessible from an internal network
  • APIs that require Internet access through a specific proxy
• Proxy support is limited to HTTP/HTTPS
• No SOCKS5 proxy support

Proposed Improvement

Introduce fine-grained proxy configuration, allowing:

1. Per-module or per-API proxy configuration

   • Each module or API client can define its own proxy behavior
   • Ability to disable proxy usage for specific internal APIs

2. SOCKS5 proxy support

   • In addition to HTTP and HTTPS proxies
   • Commonly required in corporate or secured environments

Goal

• Ability to assign different proxy settings per module or API
• Explicit support for SOCKS5 proxies
• Backward compatibility with the current global proxy behavior

Benefits

• Better support for enterprise network constraints
• Increased deployment flexibility
• Clear separation between internal and external network traffic

[stanfrbd]

Hi,
Very good catch.
Based on the current architecture it's a big challenge, I won't lie to you: this will be tough to implement if that's engine based.

It's all about configuration, and I was thinking lately about doing stuff like local cache for each engine, introducing retry, customizing timeout...

This will have a huge impact on the codebase and config (breaking changes) and I honestly think it will be long.

If the project has some help, why not :)
As you may have noticed this is a small project, but I'm very motivated!

[ubahmapk]

Ooh. This is interesting.

One change that might make this easier is switching from the 'requests' library to httpx.

That supports some pretty advanced routing (which I have admittedly not played with yet).

This would still be quite the lift, but I can see the potential.