fix(ext/node): better dns.lookup compatibility

[kt3k]

This PR changes the implementation of dns.lookup (of node compat) to use getaddrinfo (GaiResolver) instead of hickory-dns. This should provide more compatibility for the edge cases like #27670, etc as Node.js also uses getaddrinfo internally.

This fixes #27670
This could possibly have effect to #27642, #27384, and #27803

---

This PR also fixes the permission requirement for net.connect(hostname) and http.request("http://" + hostname). Currently we require net permission to DNS name servers, and also net permission to resolved IP addresses. However that is very different from net permission requirement for fetch API call (This caused the issue #27634). Now this change requires net permission to hostname at dns.lookup call and that call implicitly gives net permission of resolved IP addresses. With these changes, the permission requirement for http.request(url) is now the same as fetch(url).

This fixes #27634

---

Remaining:

• leak of op_getaddrinfo happens in unit_node/http_test in a flaky way
• add net permission check for 'hostname'
• skip net permission check for ip addressed if they are returned from dns.lookup result (because they are already granted via net permission check in dns.lookup (getaddrinfo))
• port large dns response test from fix(ext/net): enable EDNS0 for Deno.resolveDns #27735
• add check of permission requirement of http(s).request
• op_tls_start perm issue

[kt3k]

I'll also try to implement net permission checks for dns.lookup (op_getaddrinfo) (which checks the net permission with hostnames, not name servers or config files).