Take advantage of flight recorder in tests
Tests should enable all existing log scopes for the flight recorder. When a test fails, the flight recorder log needs to be dumped. This may provide valuable insight into why the test failed.
For tests to be able to do this, we probably need more wet_*()
API for setting up the scopes and maybe triggering the dump. !287 (merged) adds a piece of test oriented API, and this could go alongside that.
This task depends on #311 and #144 for the replacement macros for asserts.