feat!: reorganize crates

[nxsaken]

Description

• closes Consider renaming the bin crates for consistency #4915
  • rename iroha_client_cli to iroha_cli
  • merge iroha_wasm_builder and iroha_wasm_builder_cli
  • rename kagami to iroha_kagami (crate only, not binary)
  • rename parity_scale_cli crate to iroha_codec
• rename directories to match crate names
• flatten crate structure, move all crates to /crates
• move pytests to /pytests

Linked issue

Closes #4915, part of #2933.

Benefits

• iroha_cli a bit more convenient to install
• iroha_wasm_builder more convenient to install
• kagami no longer conflicts with an existing crate
• directories predictably match crate names
• iroha_trigger and iroha_executor no longer hidden inside iroha_smart_contract

Checklist

• I've read CONTRIBUTING.md
• I've used the standard signed-off commit format (or will squash just before merging)
• All applicable CI checks pass (or I promised to make them pass later)
• (optional) I've written unit tests for the code changes
• I replied to all comments after code review, marking all implemented changes with thumbs up

[mversic]

I suggest to name iroha_decode instead of iroha_parity_scale_cli. The former is implementation agnostic

[nxsaken]

iroha_codec maybe?

[0x009922]

I would advocate to go even further with flattening: to lift crates such as iroha_config/base, iroha_schema/derive etc to the top level as well and keep the crates structure completely flat.

Also what about nesting all crates specifically into /crates directory or something?

I also don't see a good reason why pytests (for client and torii) are located next to the respective crates. I mean, yes, the crates are indeed respective, but related pytests have nothing to do with the crates - they are integrational tests interacting with bare-metal running Iroha peer. Thus, I'd advocate to put them somewhere on the top level as well and avoid their unnecessarily deep nesting.