Investigate test differences on the bots

[timvandermeij]

In PR #18921 we noticed lots of reference test failures on Windows, but found that they already occurred two days earlier in PR #18918. The last working run was found to be in PR #18905 from five days ago, so something changed in Firefox in the meantime even though we used Firefox 133 for all runs.

Moreover, in PR #18921 we noticed Chrome on Linux timing out in the logs, which caused errors to be reported: TEST-UNEXPECTED-FAIL | test failed chrome has not responded in 120s.

To verify that the problems were not caused by PR #18921 I made a dummy PR that shows the same two issues: #18926.

We should investigate what changed to cause all differences on the Windows bot and what happened with Chrome on the Linux bot. @calixteman Could you perhaps have a look at this?

[calixteman]

Few days ago (thursday) I deleted the firefox binary on the two bots in order to have an update of nightly with a fix I wrote to remove a failure which was polluting the logs:

JavaScript error: chrome://remote/content/shared/listeners/CachedResourceListener.sys.mjs, line 65: NS_NOINTERFACE: Component returned failure code: 0x80004002 (NS_NOINTERFACE)