Customise log level.

[ruseinov]

It would be nice to be able to customize log level for tracing-test. I've got an application pretty heavy on GPU tracing and it simply crashes the test with SIGSEGV. #[tracing-test(DEBUG)] would be a nice to have. Having the default level at tracing is very limiting.

[mothran]

Just wanted to chime in here as +1 this, I know https://github.com/dbrgn/tracing-test/issues/28 covered it already but it would be nice for both test perf and readability to toggle the level down from trace. I have unit tests that generation millions of trace lines and it causes github action UI's to break trying to read the cargo test output (or really on the shell as well).

[taladar]

It would also be useful to have this ability for integration tests (where no-env-filter is basically required) to be able to tone down third party crate log levels, e.g. in frontend tests with chromiumoxide basically the entirety of the CDP protocol exchange is logged for me, making the output much less readable.