Implement human-readable bytes in the config

[0x009922]

Description

Actually implement parsing from a human-readable string for HumanBytes:

iroha/config/base/src/lib.rs

Lines 36 to 38 in 9644767

	/// Representation of amount of bytes, parseable from a human-readable string.
	#[derive(Debug, Copy, Clone, Deserialize, Serialize)]
	pub struct HumanBytes<T: num_traits::int::PrimInt>(pub T);

Specification

Here is an excerpt from the config reference draft:

Bytes amount is specified as a human-readable string:

# 42 bytes
value1 = "42B"

# 1 kilobyte = 1000 bytes
value2 = "1KB"

# 1 kilobyte (binary format) = 1024 bytes
value3 = "1KiB"

# Sum of multiple
value4 = "1GB 5MB"

Iroha can parse sizes in bytes, kilobytes (K), megabytes (M), gigabytes (G), terabytes (T),
and petabytes (P).

The format of suffixes:

• {size}iB: Binary size
• {size}B: Decimal size

I used humanfriendly Python package as a reference.

Also

• kb, kB, KiB… What’s Up With That? | Pacoup.com
• Implement human-readable durations in the config #4294

[mversic]

as discussed hyperledger/iroha-2-docs#392 I'm not sure we want to complicate config files. Simple fixed suffix on the field name should suffice IMO. We need to discuss this before proceeding

[DCNick3]

I am in favor of having human-readable suffixes in config, this makes it much easier to write large values by hand.

Oftentimes, when a large value is needed, you would still end up having a comment to explain what the value actually is, like max_transfer_bytes = 1048576 # 1 MiB, so having this natively supported by the config system is better UX IMO.

Same opinion on the #4294 with the same arguments, time_value = "1h" is better than time_value_ms = 3600000 # 1 hour