[suggestion] Fallible setters for configuration parameters

[appetrosyan]

Feature request

We should add fallible setters as configuration builder value sanity checks.

Example:

iroha_config::genesis::ConfigurationBuilder::default()
        .set_gossip_period_ms(1<<127)

is a questionable value. We should ask the user of the library to handle the insane value but not refuse them the ability to still set it. So an API would look like this

iroha_config::genesis::ConfigurationBuilder::default()
        .set_gossip_period_ms(1<<127)
        .map_err(|e| e.compromised_value())
        .unwrap()

• Produces the same reference, so setters can be chained.
• Produces the ConfigurationBuilder with the insane value set via compromised_value.
• Is still an error, so we have the option to halt, forward and ignore (as here).

Motivation

The earlier we catch an error, the easier it is to handle. This approach forces the user to be aware that not all values are acceptable, and to handle the check in Rust-y way.

Who can help?

@appetrosyan

[mversic]

related to #4282 . IMO configuration should be immutable, i.e. no setters. Setters should be defined on the configuration builder only