Fix XDM tests which occasionally timeout in CI

[teor2345]

Two tests hung on macOS:

SLOW [>5820.000s] domain-client-operator tests::test_xdm_channel_allowlist_removed_after_xdm_resp_relaying
SLOW [>5820.000s] domain-client-operator tests::test_xdm_false_invalid_fraud_proof

Would be nice for someone to dedicate time to fix these flaky tests, they fail way too often for my liking.

Originally posted by @nazar-pc in #3561 (comment)

This seems to be happening more often after the 2025-05-31 nightly compiler update and 2024 edition update in PR #3535. (We don't know which one caused it, because the updates were combined into a single PR.)

Possible Causes

• XDM relayer state
• peer bans, caused by multiple block requests, caused by request timeouts or slow block processing, caused by heavy CPU load from concurrent tests

See these comments for a discussion of the possible causes:

• Fix XDM tests which occasionally timeout in CI #3562 (comment)

[teor2345]

Happened again in the PR #3563 merge queue, but just for test_xdm_channel_allowlist_removed_after_xdm_resp_relaying:
https://github.com/autonomys/subspace/actions/runs/15553827318/job/43789726105#step:10:1546

Edit:
And also on Windows in the PR #3573 merge queue for test_xdm_channel_allowlist_removed_after_xdm_req_relaying:
https://github.com/autonomys/subspace/actions/runs/15572010974/job/43849693529#step:11:1539

[teor2345]

Failed on Windows in the merge queue for #3590:

SLOW [>6240.000s] domain-client-operator tests::test_xdm_between_domains_should_work

https://github.com/autonomys/subspace/actions/runs/15720917384/job/44301530441#step:11:1546

[teor2345]

Failed on macOS in #3592 CI:

SLOW [>6120.000s] domain-client-operator tests::test_xdm_channel_allowlist_removed_after_xdm_req_relaying

https://github.com/autonomys/subspace/actions/runs/15724897293/job/44312703770?pr=3592#step:11:2468

[teor2345]

@NingLin-P do you know why these tests are failing?

[NingLin-P]

@NingLin-P do you know why these tests are failing?

I haven't investigated any of these yet, but I suspect it is related to the race condition between the XDM relayer and the test runner, because the relayer is running concurrently, and it maintains some local states (e.g. the channel state) to filter XDM. If an XDM that is expected by the test is filtered by the relayer and never relayed, then the test will wait for the XDM until timeout.