feat: add dynamic interface management to handle network disconnects

[DerAndereAndi]

This change fixes infinite warning logs when network interfaces disconnect
during mDNS operations. Previously, the code would continue attempting to
send to disconnected interfaces, generating warnings on every attempt.

Key changes:

• Add InterfaceManager to track active/failed interfaces with adaptive backoff
• Add error classification (isInterfaceGone) to detect interface failures
• Update Client and Server to use InterfaceManager for dynamic iteration
• Fix Windows conn wrappers to return errors instead of logging them
• Add integration tests that simulate the original disconnect scenario

The fix uses separate IPv4/IPv6 managers to prevent cross-protocol failure
cascades. When an interface fails with ENXIO, ENETDOWN, or similar errors,
it's immediately removed from the active set. Recovery is attempted with
adaptive backoff (1s, 5s, 30s) when interfaces reappear.

This required the PR #3
It fixes #1

[kirollosnct]

Hello,

The CPU spinning bug and warning spam appear to be resolved, and everything has been running smoothly overall.

I have a question regarding the recovered interfaces in server.go: once an interface is recovered, why don't we attempt to reconnect to it; similar to the client?

[DerAndereAndi]

This is an oversight. Please feel free to add it :)

[kirollosnct]

I added another change to handle a case in the zeroconf client. The issue was that If the network interface is only limited to either IPv4/IPv6, the client would return an error and does not continue the setup with the available protocol.