feat(cli): add iroha transaction get and other important commands

[s8sato]

Context

Implements essential but previously missing commands in the client CLI. See Command Line Help

• Instructions Register<Trigger> ExecuteTrigger Custom remain unimplemented
• Queries FindAccountsWithAsset FindBlocks FindBlockHeaders remain unimplemented
• Also closes Implement Transfer Asset Definition in Iroha Client CLI #4077
• Provides a prototype for API to set parameters through CLI #4820
• Also closes docs: raw query predicate and selector examples #5294
• Also closes [BUG] Log instruction fails to serialize due to non-sensical #[serde(flatten)] on the level field #5305

Migration Guide

Some commands are changed in usage or behavior:

• iroha json query -> iroha query stdin
• iroha json transaction -> iroha transaction stdin
• iroha wasm -> iroha transaction wasm
• iroha * metadata -> iroha * meta
• iroha asset
  • get-key-value -> getkv
  • set-key-value -> setkv
  • remove-key-value -> removekv
• iroha events
  • data -> state
  • transaction-pipeline -> transaction
  • block-pipeline -> block
  • execute-trigger -> trigger-execute
  • trigger-completed -> trigger-complete
• iroha * list all -> iroha * list all --verbose
• iroha * list all lists only IDs and is intended to be used in combination with iroha * get --id, which retrieves the details of a single entry.

---

Checklist

• I've read CONTRIBUTING.md.
• All review comments have been resolved.
• All CI checks pass.

[s8sato]

Delegate the usage description to an auto-generated Command-Line Help

[s8sato]

snake_case for consistency with FindParameters query result to cut and reuse it as SetParameter input

[s8sato]

If SDKs already implement SetParameter I'd revert this change @0x009922 @mversic

    #[serde(rename_all = "snake_case")]
    pub enum Parameter {

[0x009922]

Iroha JS supports this, but I am not sure I understand your point and what's the issue here. Could you help me understand?

[s8sato]

That is, for example,

{
  "Sumeragi": {
    "BlockTimeMs": 2001
  }
}

will be failing to deserialize to SumeragiParameter

[s8sato]

Some #[serde(...)] attributes don't change the schema, so it seems easy for them to silently break the API

[s8sato]

I'm not sure if this follows the backporting workflow @mversic

Also,

2. Update CHANGELOG in a separate commit (we must have an entry for patch versions in the main branch as well)

Why do we update the CHANGELOG.md in the main branch for every minor version change due to backporting? Wouldn't it be sufficient to update it only in the release branches?