Use ok_or_else for lazy error logging in DNS resolution

Optimizes the DNS resolver setup by deferring log execution until an
actual failure occurs.

Changes:
- Replaced `ok_or` with `ok_or_else` when resolving DNS server
  addresses.
  evaluation and unnecessary string formatting on successful builds.

This ensures that logging overhead and string interpolation are only
incurred during error states, rather than being evaluated on every
successful initialization.

Author: chuksys

src/builder.rs

@@ -1757,7 +1757,7 @@ fn build_with_store_internal(
 				.to_socket_addrs()
 				.map_err(|_| BuildError::DNSResolverSetupFailed)?
 				.next()
-				.ok_or({
+				.ok_or_else(|| {
 					log_error!(logger, "No valid address found for: {}", dns_server_address);
 					BuildError::DNSResolverSetupFailed
 				})?;