Split short name functionality into standalone crate

[alice-i-cecile]

I was wondering whether the new dependency edge from bevy_utils to bevy_reflect would have a negative impact on compilation time. Looking at the output of cargo build --timing, it currently does not, as bevy_reflect is bottlenecked by syn->serde->glam.

Alternatively this could go into an entirely different crate. Which is what I needed a while ago for bevy_mod_debugdump so I put the function into a small crate pretty-type-name. We could just use that, unless we want to keep the non-bevy-maintained dependency count low.

Originally posted by @jakobhellermann in #5174 (comment)

bevy_utils is a hodge podge, and this type name parsing functionality is generally useful.

We should consider splitting this functionality out into a small crate under the Bevy org, so it can be easily used in other projects.

This functionality is likely to be extremely stable and has little value to the average Bevy end user, so it does not need to live in the monorepo.