feat: enable sign ext for wasm generated with rust 1.70

[loloicci]

Description

This PR enable sign-ext feature of parity wasm.
This allows wasm to use some additional operators which are sometimes used in wasm generated with rust1.70.

This fix #338.
And, this will be replaced with wasmparser in a feature version (CosmWasm/cosmwasm#1786).

Types of changes

• Bug fix (changes which fixes an issue)
• New feature (changes which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• ETC (build, ci, docs, perf, refactor, style, test)

Checklist

• I followed the contributing guidelines.
• I have updated the documentation accordingly. (not needed)
• I have added tests to cover my changes.
• The PR title and commits are followed conventional commit form.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.
1 out of 2 committers have signed the CLA.

✅ loloicci
❌ webmaster128
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[tkxkd0159]

Why don't we replace parity-wasm with wasmer::wasmparser?
Upstream already applied it and I assume there is no dependency to apply this.

ref. CosmWasm/cosmwasm#1786

[170210]

@tkxkd0159 It has already been merged into the bump_1.5.1 branch, do you mean that we need to merge it into the main branch first? https://github.com/Finschia/cosmwasm/blob/feat/bump_1.5.1/packages/vm/src/cache.rs#L17

[loloicci]

@tkxkd0159

Why don't we replace parity-wasm with wasmer::wasmparser?

This is because some interfaces of wasmparser in wasmer 4.1.0 used by CosmWasm/cosmwasm#1786 is not compatible with wasmer 2.3.0 which we use in main.
So, as I said in the description, this will be replaced in future version.

this will be replaced with wasmparser in a feature version (CosmWasm/cosmwasm#1786).

[tkxkd0159]

@tkxkd0159

Why don't we replace parity-wasm with wasmer::wasmparser?

This is because some interfaces of wasmparser in wasmer 4.1.0 used by CosmWasm/cosmwasm#1786 is not compatible with wasmer 2.3.0 which we use in main. So, as I said in the description, this will be replaced in future version.

this will be replaced with wasmparser in a feature version (CosmWasm/cosmwasm#1786).

Okay, I understand now. LGTM