Upgrade Wasmer to 0.17.0 and upgrade downcasting of errors

[ilblackdragon]

We need to upgrade to Wasmer 0.17.0 and upgrade downcasting of errors such that we can diffirentiate between host and guest panics, see: wasmerio/wasmer#1328.
0.17.0 also includes fixes for the following critical bugs:
wasmerio/wasmer#1436
wasmerio/wasmer#1412

And it includes NaN canonicalization: wasmerio/wasmer#1303

For more context see #2316 (comment) . Currently we are printing "unknown" error all the time. See the report below.

---

Receiving output in nearcore:

Bad error case! Output is non-deterministic TypeId { t: 7549865886324542212 } "unknown error"

Steps to repro:

• Deploy contract staking-contract from Staking contract for delegation nearprotocol/stakewars#110
• Create two accounts my_validator and acc1. Deposit 100 NEAR to acc1.
• Call near call my_validator deposit '' --account_id acc1 --amount 10

Output from near:

Error:  { Error: The used access key requires exactly one FunctionCall action
    at Object.parseRpcError (/usr/local/lib/node_modules/near-shell/node_modules/nearlib/lib/utils/rpc_errors.js:25:19)
    at Account.signAndSendTransaction (/usr/local/lib/node_modules/near-shell/node_modules/nearlib/lib/account.js:87:36)
    at process._tickCallback (internal/process/next_tick.js:68:7) type: 'ActionError', index: 0 }

[ilblackdragon]

Ok, isolated it to having prints in my contracts.
We should probably either block contracts with prints or make this errors more eligible.

The "used access key requires" is different errors, both in nearlib and somewhere else. Investigating.

[ilblackdragon]

Filed the error as separate issue in nearlib - near/near-api-js#210

[evgenykuzyakov]

The first part:

Bad error case! Output is non-deterministic TypeId { t: 7549865886324542212 } "unknown error"

Might be related to Wasm Traps. It should be addressed by near/near-sdk-rs#73

[ilblackdragon]

@evgenykuzyakov can you test and closed if it's fixed?

[MaksymZavershynskyi]

I think it is still happening. I asked Wasmer to clarify why is it happening.

This is blocked by Wasmer response and therefore I assigned pessimistic ETA in case modifications in Wasmer are needed.

[evgenykuzyakov]

I'm not working on this

[MaksymZavershynskyi]

Blocked by: wasmerio/wasmer#1328

[MaksymZavershynskyi]

Should be resolved by #2316

[lexfrl]

Should be resolved by #2316

Unfortunately, Wasmer doesn't return ExceptionCode's today (for single pass backend). Let's wait for wasmerio/wasmer#1328

[MaksymZavershynskyi]

More context:
#2316 (comment)

[MaksymZavershynskyi]

Blocked by wasmerio/wasmer#1338

[olonho]

Seems due to rust-lang/rust#68905 we have to update the Rust toolchain.

[olonho]

nightly-2020-05-16 works fine.