fix(wasm-builder): allow building with stable toolchain

[StackOverflowExcept1on]

This PR fixes build with +stable

Tests:

cd utils/wasm-builder/test-program
cargo +stable build --release

@gear-tech/dev

[clearloop]

plz provide a test of stable build with test-program btw

https://github.com/gear-tech/gear/tree/master/utils/wasm-builder/test-program

mb override the rust-toolchain of this crate or using environment to do the test

[StackOverflowExcept1on]

We have smoke tests in https://github.com/gear-tech/gear/blob/master/utils/wasm-builder/tests/smoke.rs but it's marked with ignored to do not waste time on make pre-commit. It's tested every Monday here: https://github.com/gear-tech/gear/actions/workflows/time-consuming-tests.yml

I think we can test this program with both toolchains in time-consuming-tests environment.

For the check action, we can also add cargo +stable build

gear/.github/workflows/check.yml

Lines 61 to 62 in a34fcfc

	- name: "Check: Compiling gstd on stable"
	run: cargo +stable check -p gstd

[NikVolf]

We have smoke tests in https://github.com/gear-tech/gear/blob/master/utils/wasm-builder/tests/smoke.rs but it's marked with ignored to do not waste time on make pre-commit. It's tested every Monday here: https://github.com/gear-tech/gear/actions/workflows/time-consuming-tests.yml

I think we can test this program with both toolchains in time-consuming-tests environment.

For the check action, we can also add cargo +stable build

gear/.github/workflows/check.yml

Lines 61 to 62 in a34fcfc

	- name: "Check: Compiling gstd on stable"
	run: cargo +stable check -p gstd

yeah, add this pls

[clearloop]

gear/.github/workflows/check.yml

Lines 61 to 62 in a34fcfc

	- name: "Check: Compiling gstd on stable"
	run: cargo +stable check -p gstd

wait, I believe this test should be

cargo +stable check -p gstd --target wasm32-unknown-unkown

the current

cargo +stable check -p gstd 

missed the wasm32-unknown-unknown target, so we failed to find the issue in CI

[StackOverflowExcept1on]

@clearloop I think we shouldn't use --target because the wasm-builder will switch to nightly toolchain.

[breathx]

@ark0f please take a look

[StackOverflowExcept1on]

Will be continued after #3527

[breathx]

@StackOverflowExcept1on @ark0f @breathx
Relates #3527 (review)

# Wasm builder changes
# Use the same toolchain: `gear_wasm_builder::build::<Metadata>();`
# Use recommended nightly: `gear_wasm_builder::recommended_nightly::<Metadata>();` // ERROR IF VERSION IS DIFFERENT