gel-cli requires /etc/resolv.conf to exist even when it's not needed

I was trying to run Gel Cli in a sandboxed build pipeline (Nix build) without network, talking to a locally spawned server on `127.0.0.1`. I noticed it panics when `/etc/resolv.conf` does not exist even when it's not needed for anything — I connect to the server through a direct IP `127.0.0.1`. Gel Cli works if I create a dummy `/etc/resolv.conf`.

Seems like an unnecessary dependency, and `gel` could only require that file when it's actually needed.

Start by tracing Gel CLI startup and connection setup to find where /etc/resolv.conf is accessed, then reproduce the issue in a sandbox without that file while connecting to 127.0.0.1. Done means direct-IP connections no longer panic without /etc/resolv.conf, while name-based connections still retain their required resolution behavior.

Written by the indexing model from the issue text.