[refactor] #4045: Use concrete key types

[Arjentix]

Description

• PublicKey and PrivateKey are now enums with explicit key types. No invalid state is possible
• Fixed some tests
• Fixed now useless errors signatures of depended code
• amcl_wrapper replaced with w3f-bls
• iroha_crypto is now compatible with no-std and WASM
• Fixed some clippy lints

Linked issue

• Closes [suggestion]: Use concrete key types in iroha_crypto #4045
• Closes Consider signing by KeyPair reference not by value #4199
• Addresses query validation in no_std #3714
• Openned [suggestion] Stop encoding X25519 keys as Ed25519 #4174
• Openned [feature] Cross-crate WASM-compatible logging system #4241

Benefits

• More robust solution because now we are sure that stored keys are valid
• No more errors are possible when creating keys or signing
• Test are more real now

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]

Currently it's impossible to build Executor or any wasm, because used crypto libraries are feature-gated, meaning that even PublicKey and PrivateKey cannot be represented as is in WASM.

Solutions I see:

* Let WASM have all crypto code and remove feature-gate. Unused code will likely be optimized by Rust, but I'm not sure.

* Have another `PublicKey` and `PrivateKey` for WASM types which will be compatible with types from Host in terms of encoding and serialization

For any of this solutions I would like to hear other opiniont, especially from @mversic .

I would try to get PublicKey/PrivateKey work in no-std. If that is not possible, then we can try using std in wasm. The last thing is making FFI calls

[DCNick3]

Very nice to see all those .unwrap()'s gone!