Websockets connect to port 80 by default

[crusaderky]

Blocks #7768

[github-actions]

Unit Test Results

See test report for an extended history of previous test failures. This is useful for diagnosing flaky tests.

       26 files  ±  0         26 suites  ±0   14h 37m 26s ⏱️ + 38m 8s
  3 554 tests +  4    3 432 ✔️  -   7     106 💤 ±0  16 ❌ +11 
44 962 runs  +52  42 632 ✔️  - 33  2 242 💤 +2  88 ❌ +83 

For more details on these failures, see this check.

Results for commit 986c01f. ± Comparison against base commit 600b993.

This pull request removes 4 and adds 8 tests. Note that renamed tests count towards both.

distributed.comm.tests.test_ws ‑ test_connection_made_with_extra_conn_args[ws://-False]
distributed.comm.tests.test_ws ‑ test_connection_made_with_extra_conn_args[ws://-True]
distributed.comm.tests.test_ws ‑ test_connection_made_with_extra_conn_args[wss://-False]
distributed.comm.tests.test_ws ‑ test_connection_made_with_extra_conn_args[wss://-True]

distributed.comm.tests.test_ws ‑ test_connection_made_with_extra_conn_args[False-ws://]
distributed.comm.tests.test_ws ‑ test_connection_made_with_extra_conn_args[False-wss://]
distributed.comm.tests.test_ws ‑ test_connection_made_with_extra_conn_args[True-ws://]
distributed.comm.tests.test_ws ‑ test_connection_made_with_extra_conn_args[True-wss://]
distributed.comm.tests.test_ws ‑ test_implicit_port[-80-ws://]
distributed.comm.tests.test_ws ‑ test_implicit_port[-80-wss://]
distributed.comm.tests.test_ws ‑ test_implicit_port[:123-123-ws://]
distributed.comm.tests.test_ws ‑ test_implicit_port[:123-123-wss://]

[crusaderky]

Turns out that the scheduler thoroughly relies on these functions to raise ValueError to indicate that there's no port. I'll find out a different avenue.