This PR re-enables node compat test run with the below cases excluded:
- flaky tests
- `parallel/test-dgram-connect-send-empty-packet.js`
- `parallel/test-fs-read-stream-concurrent-reads.js`
- `parallel/test-http-agent-maxtotalsockets.js`
- internet dependent tests
- `internet/test-dgram-connect.js`
- `internet/test-dns-lookup.js`
- `internet/test-dns-promises-resolve.js`
- `internet/test-dns-regress-6244.js`
- `internet/test-dns-setserver-in-callback-of-resolve4.js`
- `internet/test-http-dns-fail.js`
- `internet/test-http-https-default-ports.js`
- `internet/test-https-autoselectfamily-slow-timeout.js`
- `internet/test-inspector-help-page.js`
- `internet/test-net-autoselectfamily-events-timeout.js`
- `internet/test-net-connect-unref.js`
- `internet/test-tls-autoselectfamily-servername.js`
The list (`tests/node_compat/config.toml`) might include a few more
flaky tests. Let's keep excluding such test as they are found.
This commit removes all occurrences of `--unstable` flag
from all the tests that are run in CI.
Turns out none of the tests actually required that flag
anymore.
It's not clear to me how these tests worked correctly on CI,
but they were failing hard locally because of two problems:
- missing env var that tests URL for fake npm registry
- trying to run a directory that contains native Node.js tests that
require a special harness
