build(wasm_samples): pre-compiled wasm_samples

[0x009922]

Context

Split from #5087

There are numerous invocations of iroha_wasm_builder library interface from within tests/benches/examples.

Problems:

• Critical: interferes with -C instrument-coverage rustc flag (refactor!: black-box integration tests #5087 (comment)), which is set when we run tests with coverage.
• Inconsistent test runs: they are slow at first (while building WASMs for the first time), then fast. Reduces ability to set stricter time policies (which we could with Nextest).
• Code duplication

Solution

• No running of iroha_wasm_builder from tests. It makes possible to run all tests with coverage in a single CI run (that was achieved in refactor!: black-box integration tests #5087 (comment))
• One script to rule them all build all wasm_samples, both locally and CI
• Unified API: iroha_test_samples::load_sample_wasm("default_executor") -> WasmSmartContract
  • Has a descriptive error message.
• Build all WASMs in one CI run

Migration Guide (optional)

For developers: ./scripts/build_wasm_samples.sh is a single command for you to prepare all WASMs and defaults/executor.wasm. You need to run it before running tests that depend on WASM samples.

---

Review notes (optional)

None

Checklist

• I've read CONTRIBUTING.md.
• (optional) I've written unit tests for the code changes.
• All review comments have been resolved.
• All CI checks pass.

[mversic]

I notice you didn't remove the wasm build from the build scripts such as wasm_samples/multisig_register/build.rs?

[0x009922]

I notice you didn't remove the wasm build from the build scripts such as wasm_samples/multisig_register/build.rs?

Yes, I left it as-is. It just works, and I don't know how to be with it: shall multisig_register not include another WASM inside, but get it from somewhere else? E.g. it could be supplied as a payload with ExecuteTrigger ISI.

[mversic]

I notice you didn't remove the wasm build from the build scripts such as wasm_samples/multisig_register/build.rs?

Yes, I left it as-is. It just works, and I don't know how to be with it: shall multisig_register not include another WASM inside, but get it from somewhere else? E.g. it could be supplied as a payload with ExecuteTrigger ISI.

yeah, it's ok. Building multisig_register will first build multisig.wasm