Add `bind` config option and support for HTTP

[amunra]

Add support for specifing a NIC when using the HTTP interface.
Ensure this is exposed through to the Python client too.
(This is a customer request: https://questdb-tech.slack.com/archives/C093QM6RKBJ/p1764352071911759).

[amunra]

Detail:

We use the ureq crate for HTTP connections.
Unfortunately this lib does not expose the ability to bind to a specific interface.
This is because to do this, one needs to use socket2 and ureq is trying to avoid extra dependencies.

The ureq crate does allow customising the TCP connection process. In fact we already take over the TLS logic so we can plug in custom certs.

To implement bind we'd need to take plug in the TCP connection process fully and establish the socket via the socket2 crate (which we already depend on) and use the same connection logic we use for TCP. After that we can hand over the established connection back to ureq.

The core of the logic is self-contained in questdb-rs/src/ingress/sender/http.rs.