[refactor] #4161: rewrite config, _minimally_

[0x009922]

Description

This PR is a complete overhaul of Iroha & Client CLI configuration. It is based on the Configuration Overhaul RFC.

Although this PR has many changes already, there are still big parts of the RFC to be completed separately.

Configuration changes

• Change format: TOML, lower-case fields
• Restructure and rename parameters for users' convenience
• Localise chain-wide parameters in the [chain_wide] section to ease further transition: [discussion] Align configuration-related instructions with the RFC #4028
• Limit set of ENV aliases for the parameters
• Support composition via extends mechanism
• Split user config view from strongly-typed internal config representation
• Emit as many errors at once as possible: collecting all missing fields, all ENV parsing failures, and semantic errors.

Subsequent changes

• Revise sample configurations:
  • remove alt branch configs (configs/peer/lts|stable, configs/client/lts|stable)
  • put client.template.toml, peer.template.toml, and prometheus.template.yaml in the root of configs. These configs are not for direct use, but rather a part of documentation.
  • move docker compose files into configs/swarm
  • move docker compose related configurations into configs/swarm as well (client.toml, genesis.json, and executor.wasm)
  • some tests & deployment docs relied to /configs directory to use client/peer configs. It was implied that the configs are actually workable and filled with everything needed. It was ambiguous. Now those places rely on /configs/swarm content.
• Update test environment:
  • test_env.py:
    • doesn't use ENVs to set configuration
    • generates a shared config, and individual configs (extending the shared one) for each peer
  • Pytests:
    • Split CLIENT_CLI_DIR (implying it has iroha_client_cli and config.json content) setting into CLIENT_CLI_BINARY and CLIENT_CLI_CONFIG
• Iroha Swarm:
  • Doesn't rely on IROHA_CONFIG variable anymore, and doesn't expect Iroha configuration to be present in the configs directory; relies only on genesis.json, and all necessary configs are set in ENV.
  • TODO: allow users to customise configuration? For all peers or for individual ones somehow?
    • maybe via --config-shared=shared.toml --config-peer0=peer0.toml CLI
• Iroha Torii:
  • split constants (namely - URIs) into a iroha_torii_const crate for easier re-use in iroha_client. Previously those were defined in iroha_config, which is not an appropriate place for it.
• Kagami:
  • remove kagami config command, which used to produce "sample" peer/client configurations

Intentionally left issues (temporarily)

• Using Report as a universal error to not bother with errors (yet)
• Default is used for *Partials to create empty layers, while Default for actual config structures fills them with default values.

Not implemented

• Tracing of configuration: basic debug logging to track how config is read, where and what is overwritten, how final value looks like etc
• Enhanced errors:
  • emitting errors with fancy diagnostics by ariadne, spans to config files and/or ENVs, hints etc
  • "lazy" parsing of TOML with multiple-errors emitting
• Human-readable durations and byte sizes; although I put HumanDuration and HumanBytes as stubs for future.

Post-merge

Upon merging of this PR, create these as separate issues:

• Create a separate general purpose configuration crate (project soukousei), move some of iroha_config_base's stuff there, define a procmacro to generate boilerplate: [suggestion] Split generic configuration functionality from iroha_config_base into a standalone library #4297
  • Remove merge dependency and introduce an in-house macro for this Remove merge dependency #4298
• Enhance errors (might be part of the previous one): Enhance configuration errors #4299
  • use fancy diagnostics and hints
  • use spans to source files and envs
  • don't use eyre::Report as a universal error
• Remove chain-wide configuration from here: [discussion] Align configuration-related instructions with the RFC #4028
• Cover client.template.toml and peer.template.toml with some tests: [suggestion] Cover template configurations with tests #4288
• Implement config tracing as per RFC Implement config tracing #4300
• Ensure how Snapshot uses its path from configuration: it should automatically create the top-level directory for it, but not upper. It allows specifying ./storage/snapshot as a default value, which is convenient. [suggestion] Snapshot configuration - ensure it creates a directory for itself #4296
• Human-readable durations and bytes: Implement human-readable durations in the config #4294, Implement human-readable bytes in the config #4295
• Update reference: Tracking Issue for Configuration Reference as per RFC iroha-2-docs#392
• Change PrivateKey deserialisation format: allow algorithm and payload fields, deprecate digest_function: [suggestion] (de-)serialize PrivateKey with algorithm field #4287
• Remove parse_display crate from dependencies: [suggestion] Remove parse_display dependency entirely #4290
• Use nonzero_ext across workspace: [suggestion] Use nonzero_ext across workspace #4289
• [discussion] Update how Snapshots are configured #4059
• Immutable configuration #4282
• Update executor in genesis.json: rename to executor_file for consistency; drop inline mode support entirely. [suggestion] Update executor config in the genesis block #4291
• Consider renaming configs/swarm to configs/docker_compose: [discussion] Rename configs/swarm? #4293
• Actualise Dockerfiles and panic_on_invalid_genesis.sh test: Actualise Dockerfiles with the new config system #4292, panic_on_invalid_genesis.sh is outdated #4301

Linked issues

Closes #4161, #3499, #3500, #3501, #3504, #3358