dns: validate port range in setServers()

[Renegade334]

As per #65009 (review).

dns.setServers() currently has the following shenanigans with out-of-range port numbers:

• uint16 overflow (seems version-/platform-dependent)

  dns.setServers(['1.2.3.4:65535', '1.2.3.4:65536', '1.2.3.4:65537'])
  dns.getServers()
  [ '1.2.3.4:65535', '1.2.3.4', '1.2.3.4:1' ]

• process crash if >INT_MAX

  dns.setServers(['1.1.1.1:99999999999999999999999999'])
  // #  node[1673753]: void node::cares_wrap::(anonymous namespace)::SetServers(const FunctionCallbackInfo<Value> &) at ../src/cares_wrap.cc:2164
  // #  Assertion failed: portValue->Int32Value(env->context()).FromJust()

(the latter of these is not addressed by #65009)

[nodejs-github-bot]

Review requested:

• @nodejs/net

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 90.30%. Comparing base (1576cb8) to head (16f5b73).
⚠️ Report is 10 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #65021      +/-   ##
==========================================
- Coverage   90.30%   90.30%   -0.01%     
==========================================
  Files         759      759              
  Lines      247634   247636       +2     
  Branches    46684    46697      +13     
==========================================
- Hits       223630   223629       -1     
- Misses      15467    15468       +1     
- Partials     8537     8539       +2     

Files with missing lines	Coverage Δ
lib/internal/dns/utils.js	99.44% <100.00%> (+<0.01%)	⬆️

... and 31 files with indirect coverage changes

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[nodejs-github-bot]

CI: https://ci.nodejs.org/job/node-test-pull-request/75476/