Check some of the older CI runs to see if there are flaky tests and ideally fix the flakiness

[manuelwedler]

In the node-v16 CI job we have a few tests that are flaky, meaning that they sometimes pass and sometimes not. It would be nice to check which these tests are, and if possible make them deterministically passing or failing.

If there are tests that are expected to be flaky, since we cannot guarantee an external service to be up, then it makes sense to isolate these in their own CI job. That way we can distinguish more easily between an error on our side and a flaky test.
This issue should only be about identifying the flaky tests. For moving flaky tests to another CI job, we can create a follow up issue, once we are more clear on how we want to structure all of the tests.

[manuelwedler]

Closing as the tests are constantly successful for a while.