Switch to full wasm execution

[bkchr]

Description

Stops using the NativeElseWasmExecutor and replaces it with the WasmExecutor. Thus, block production/import etc is also using the wasm execution as the validation on the relay chain.

Fixes paritytech/polkadot-sdk#4808

Changes and Descriptions

[List your changes here]

Checklist:

• I have added Rust doc comments to structs, enums, traits and functions
• I have made corresponding changes to the documentation
• I have performed a self-review of my code
• I have added tests that prove my fix is effective or that my feature works

[mustermeiszer]

First of all, thanks a lot for all the effort taken into researching and solving this. I am still not sure I follow the process here:

• Should we anyways switch to full wasm execution - we could also defer to use the MaxEncodedLen in the feed size?
• Why is the chain able to make progress?
  *. IIUC the parachain tried to include said extrinsic in the block - events were popping up - but the relay-chain could not validate such block - still block production continued, just without said extrinsic being included.

[bkchr]

• Should we anyways switch to full wasm execution - we could also defer to use the MaxEncodedLen in the feed size?

Yes you should switch to full wasm execution. This is the future any way and the NativeElseWasmExecutor is tagged as deprecated in master already.

• Why is the chain able to make progress?
  *. IIUC the parachain tried to include said extrinsic in the block - events were popping up - but the relay-chain could not validate such block - still block production continued, just without said extrinsic being included.

Yeah without the transaction it could progress, because then the mismatch wasn't triggered.

[mustermeiszer]

Replaced by #1882. All kudos to @bkchr!