[codex] retire CI-env parity fixture skips

[andrewtdiz]

Linked issues

• Closes Parity CI: environment-only failures (server fixtures, npm install, runner-specific) #1634

Summary

This PR retires the stale ci-env known-failure entries owned by #1634. The legacy top-level net fixtures already have local companion servers, but readiness polling depended on runner nc; the Ramda-named fixture is now a self-contained mini-reproducer and no longer imports the package.

Changes:

• add a wait_for_tcp_port helper in run_parity_tests.sh that probes local TCP readiness with Python sockets instead of runner nc;
• apply that helper to both the top-level echo server and the per-test TLS-upgrade server;
• add missing Python/script guardrails to the TLS-upgrade helper;
• remove all Parity CI: environment-only failures (server fixtures, npm install, runner-specific) #1634 ci-env entries from test-parity/known_failures.json.

Why this batch

These entries share the same stale CI-environment classification. The net entries are companion-server lifecycle checks, and test_ramda_sum has since become a self-contained runtime mini-reproducer rather than an npm-install fixture. Keeping them together closes the #1634 skip-list cleanup without mixing runtime behavior changes.

Validation

• bash -n run_parity_tests.sh
• jq empty test-parity/known_failures.json
• cargo fmt --all -- --check
• git diff --check
• ./scripts/check_file_size.sh
• Node v26 focused parity filters, all 1 pass / 0 parity fail / 0 compile fail:
  • npm exec --yes --package=node@26 -- bash -lc './run_parity_tests.sh --filter test_issue_422_socket_connect'
  • npm exec --yes --package=node@26 -- bash -lc './run_parity_tests.sh --filter test_net_min'
  • npm exec --yes --package=node@26 -- bash -lc './run_parity_tests.sh --filter test_net_socket'
  • npm exec --yes --package=node@26 -- bash -lc './run_parity_tests.sh --filter test_net_upgrade_tls'
  • npm exec --yes --package=node@26 -- bash -lc './run_parity_tests.sh --filter test_sock_write_map'
  • npm exec --yes --package=node@26 -- bash -lc './run_parity_tests.sh --filter test_ramda_sum'

Known limitations

The TLS-upgrade fixture still uses its stored expected-output path because Node exits nonzero for this Perry-specific helper shape; the Perry expected-output comparison passes. Module-inventory and stream/web known-failure entries are unchanged.

Non-goals

No Node runtime behavior, net stdlib behavior, npm package installation, module-inventory skips, or stream/web behavior are changed here.