CI: debugging timeouts

[jbrockmendel]

Frequently I'll see a CI run has a failure where a build was cancelled after 180 minutes. I'll also sometimes see local test runs get stalled somewhere in the io tests. I'm tentatively assuming these have the same cause.

Could we configure the CI to report the PYTEST_CURRENT_TEST environment variable when a timeout occurs? cc @lithomas1

The same rabbit hole led me to some options for flaky tests:
https://learn.microsoft.com/en-us/previous-versions/azure/devops/2017/dec-11-vsts?view=tfs-2017#identify-flaky-tests
https://docs.pytest.org/en/7.1.x/explanation/flaky.html#plugins

[jbrockmendel]

Closing as not actionable.