Keep lazy connections enabled in the agent-network e2e harness

Revert the NB_LAZY_CONN=false override on the harness client and proxy
containers: with the DNS-time lazy-connection warm-up in place, the
harness resolves the endpoint first, which wakes the proxy peer before
WaitProxyPeer polls for it. Running the suite with lazy connections on
is the point — it exercises the warm-up path end to end.

e2e/harness/client.go

@@ -56,11 +56,6 @@ func StartClient(ctx context.Context, c *Combined, setupKey string) (*Client, er
 			// Match the proxy: the combined relay is WebSocket-only, so the
 			// client must use WS transport to keep a stable relay link to it.
 			"NB_RELAY_TRANSPORT": "ws",
-			// Lazy connections defer the peer dial until traffic flows, which
-			// leaves `netbird status` at "0/N Connected" and starves
-			// WaitProxyPeer. Force eager connections so the proxy peer shows
-			// Connected as soon as the tunnel is up.
-			"NB_LAZY_CONN": "false",
 		},
 		HostConfigModifier: func(hc *container.HostConfig) {
 			hc.CapAdd = append(hc.CapAdd, "NET_ADMIN", "SYS_ADMIN", "SYS_RESOURCE")

e2e/harness/proxy.go

@@ -77,10 +77,6 @@ func StartProxy(ctx context.Context, c *Combined, proxyToken string) (*Proxy, er
 			// Management is plain HTTP in-cluster, so allow the proxy token to
 			// ride a non-TLS gRPC connection.
 			"NB_PROXY_ALLOW_INSECURE": "true",
-			// Keep the embedded overlay peer eager (see the client env note):
-			// lazy connections leave peers unconnected until traffic, which
-			// starves the harness's WaitProxyPeer.
-			"NB_LAZY_CONN": "false",
 			// The combined server multiplexes the relay over WebSocket on :8080
 			// (no QUIC listener). The proxy's embedded relay client defaults to
 			// QUIC, which fails here and flaps the relay link, churning the