Adjust timeouts in jupyter cli test

[fjetter]

This test is failing pretty constantly. #8848 made things worse so I suggest increasing the timeout for this. I also put in the default ports fixture since the test requires the port 8787

If that doesn't work I'll likely skip the test since the signal it adds is only marginal and it is failing all over CI (but running locally)

[github-actions]

Unit Test Results

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

    25 files  ±    0      25 suites  ±0   10h 14m 14s ⏱️ + 46m 35s
 4 128 tests  -     2   4 015 ✅ +    4    110 💤  -  2  3 ❌  - 4 
47 668 runs  +1 408  45 551 ✅ +1 370  2 114 💤 +44  3 ❌  - 6 

For more details on these failures, see this check.

Results for commit 0b58451. ± Comparison against base commit 7d43e2f.

This pull request removes 2 tests.

distributed.cli.tests.test_dask_worker.test_listen_address_ipv6[tcp:..[ ‑ 1]:---nanny]
distributed.cli.tests.test_dask_worker.test_listen_address_ipv6[tcp:..[ ‑ 1]:---no-nanny]

[fjetter]

Well, far from conclusive but this CI job is not having a test failure for this jupyter CLI test. Merging