We recently added runtime tracing and flight recording to the Pony runtime. When discussing #4702, we came to a decision to add flight recorder to most of our CI tests.

For standard PR tests, we want to build with flight recorder for all tests. Additionally, we want to add a new "use" test that is for "vanilla" which would be building without any use definitions to make sure that works. The runtime tracing use test that currently exists will be removed as all our primary PR tests will be exercising runtime tracing. The goal of the vanilla use test(s) is to make sure we don't lose basic "it compiles" coverage. We have our use jobs run tests but that is mostly "extra". For use jobs the primary goal is to verify compilation is successful. We doubt that any use option will break tests but it is always possible.

For stress tests, we want to build with flight recorder for all the stress tests.

For all flight recorder setup we want to dump either stderr or stdout so that we can get additional information from the CI logs without having to setup grabbing file based assets and uploading somewhere.

For all tests that are running "in the debugger", we want to continue to do so.