use more levels of spans than always info

## What problem does this solve or what need does it fill?

Currently all spans from Bevy are at `info` level. This means traces with tracy quickly get very big.

## What solution would you like?

Spans can be filtered by module and by level.

Some spans could be moved to other levels, mostly `debug`, to help filtering on what someone is trying to trace
for example, in bevy_ecs, keep system spans at info, but moves tick checks to debug. that way someone debugging a rendering issue could keep system spans, but ignore other acs-internal spans.

See https://github.com/bevyengine/bevy/pull/5470 for a previous attempt, but without enabling the `trace` feature by default