Some reference implementations:

• https://dev.mysql.com/doc/refman/8.0/en/sys-format-bytes.html
• https://learn.microsoft.com/en-us/azure/data-explorer/kusto/query/format-bytesfunction
• https://pgpedia.info/p/pg_size_pretty.html
• https://clickhouse.com/docs/en/sql-reference/functions/other-functions

Before this PR, 10000 would be returned as 10.0 KB, after as 9.76 KiB (node 9.76 * 1024 = 10000).

Note that input side both styles are now supported, so both 100.0 KB, 97.6 KiB, 100000 bytes, 0.1 MB or 0.095367432 MiB are supported and the resulting settings would be roughly equivalent.

This PR makes a few opinionated choices:

• MiB instead of MB
• space between number and unit
• relevant digits are in the range 1.0-1023.9, similar to previous behaviour (it was 1.0 - 1000). We could consider going for a preferred range starting at 10.0, as postgress does, where for example 7649 kB is rendered instead of 7.6 MB

An overload for format_bytes taking the binary base was considered, but given there are other possible overloads (precision, preferred unit), I think it's safer to avoid it, also given there are the alternative methods formatReadableSize and formatReadableDecimalSize.