Add a set of memory conversion methods to bevy_utils

[alice-i-cecile]

I would actually prefer to have a function on bevy_utils that formats a memory measurement to KiB, MiB, GiB, ... depending on the value. Memory measurements will be quite common in game engines.

Originally posted by @Nilirad in #5454 (comment)

[mockersf]

I disagree, this doesn't need to be part of Bevy.

[alice-i-cecile]

Closing until we can find a clear motivation. This may fit well as a truly external crate that we import for the editor.

[mockersf]

quick search found https://crates.io/crates/unit-conversions

[IceSentry]

For the record, I didn't use it in my PR because I didn't want to add a crate for what was essentially just a multiplication in my case.

Once we start needing to show this in a more friendly manner in the future editor that crate would be a good starting point, but it doesn't have a distinction between GiB and GB which is not ideal in my opinion. It's a bit weird considering they do have KiB vs KB.

[Nilirad]

Also that crate doesn't help to automatically display the more convenient unit based on the value.

[alice-i-cecile]

We should see about PRs to fix those limitations upstream (and existing alternatives) before trying to fork IMO.

[Nilirad]

Actually, I was not thinking to do unit conversion (as returned value), but just formatting a value.

We can easily achieve it by creating a newtype on a numeric value (e.g. i64) and implement the Display trait for it that will use the most convenient binary unit (what is most convenient has to be defined). Additionally, it may also have methods such as bytes_to_string, kibibytes_to_string, as kilobytes_to_string and so on.