Change default execution strategies to Wasm

[bkchr]

This pr changes all default execution strategies to Wasm. This is basically a deprecation of the
native runtime. While the native runtime isn't removed and can still be used, it will not be used
anymore by default.

This will also improve the usage for people who want to run random commits, which most often forget
to run with --execution wasm. Otherwise they often run into storage root mismatches because of
using the native runtime.

[shawntabrizi]

Are we also using wasmtime by default?

[wigy-opensource-developer]

The README of staking-miner might need some fixup in the "Testing locally" section, too? And the bridges repo also overrides --execution in the compose files.

[bkchr]

Are we also using wasmtime by default?

If the feature is enabled, yes.

[bkchr]

The README of staking-miner might need some fixup in the "Testing locally" section, too? And the bridges repo also overrides --execution in the compose files.

This doesn't break anything, it just changes the default. You can still use the cli argument to override these values.

[xlc]

I will assume parachains doesn't need to do anything and will inherent this default once we upgrade Substrate version?

[bkchr]

Exactly. These are the default values for the cli flags. As long as you don't run your node with any --execution* flag, this will be picked up.

[bLd75]

Just a point worst mentioning: wasm strategy drastically reduces performance of archive nodes who have public exposed endpoint under high number of requests.
Archive nodes will have to explicitly set native execution.