Backport new tests from WebAssembly/spec master

[gumb0]

No description provided.

[gumb0]

Fizzy spectest runner uses these strings only for logging, so this is not much useful for us, but also doesn't hurt, so I included such changes to be closer to upstream and make future backporting potentially easier.

[gumb0]

Not sure why this is changed (maybe related to some new rules about out of bounds during instantiation https://github.com/WebAssembly/spec/blob/f607ec9a776a9e3425639f3cbe9b2d96bdc16b60/test/core/linking.wast#L395)

For us the change is optional, but if we accept it, requires the change in spectest runner (see wasmx/fizzy#750)

[gumb0]

Some more comments about backporting WebAssembly#1287

• Many "new" tests merged in binary.wast were actually duplications of old tests in binary-leb128.wast. I did not include them in cherry-pick. I removed them and some other duplications in [test] Remove duplicate tests WebAssembly/spec#1314.

• Some new tests for imported table limits were added https://github.com/WebAssembly/spec/blob/f607ec9a776a9e3425639f3cbe9b2d96bdc16b60/test/core/imports.wast#L391-L399 but they duplicate (for another module with 2 tables) the existing tests with spectest module, so I didn't cherry-pick them.

[gumb0]

It looks too complicated to try to backport WebAssembly#1287 commit's changes applicable to 1.0, so we'll be skipping it (and other post-1.0-related test commits).