test: add unit test for pop build parachain

[brunopgalvao]

Unit test for pop build parachain

[brunopgalvao]

Not sure why the CI is failing. Works fine on my machine.

[weezy20]

@brunopgalvao setup protoc on the CI. Some dependency wants that.

[AlexD10S]

Build the parachain is very slow, and now running cargo test can take a while. I opened an Issue about that a while ago: #18

Any thoughts on how to improve this? Should we add a feature flag as suggested there?

[brunopgalvao]

Looks like we do need the wasm32-unknown-unknown target:

   Compiling parachain-template-runtime v0.7.0 (/tmp/.tmp4LtFzj/runtime)
error: failed to run custom build command for `parachain-template-runtime v0.7.0 (/tmp/.tmp4LtFzj/runtime)`

Caused by:
  process didn't exit successfully: `/tmp/.tmp4LtFzj/target/release/build/parachain-template-runtime-bdf6ae77f659e646/build-script-build` (exit status: 1)
  --- stderr
  Cannot compile the WASM runtime: the `wasm32-unknown-unknown` target is not installed!
  You can install it with `rustup target add wasm32-unknown-unknown` if you're using `rustup`.
warning: build failed, waiting for other jobs to finish...
test engines::parachain_engine::tests::test_parachain_build_after_instantiating_template ... FAILED

failures:

---- engines::parachain_engine::tests::test_parachain_build_after_instantiating_template stdout ----
thread 'engines::parachain_engine::tests::test_parachain_build_after_instantiating_template' panicked at src/engines/parachain_engine.rs:129:9:
Result should be Ok
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace


failures:
    engines::parachain_engine::tests::test_parachain_build_after_instantiating_template

test result: FAILED. 5 passed; 1 failed; 0 ignored; 0 measured; 0 filtered out; finished in 1358.77s

error: test failed, to rerun pass `--bin pop`
Error: Process completed with exit code 101.

I have added it back in.

I have updated the PR according to your feedback.