Improve clarity-wasm behaviour in console

[hugocaillard]

clarity-wasm can show some stability issues so it should be possible to opt-out of clarity-wasm but keep it enabled by default to really tests clarity-wasm.

Also, it could be silent by default (avoid logging the timings).

The error message when clarity-wasm returns a different result than the interpreter can be improved as well, explain that there's is flag to disable clarity-wasm and asking to open an issue with the log output.

• add a --no-clarity-wasm flag to clarinet console
• add a --show-clarity-wasm-perf flag to clarinet console
• improve clarity-wasm warning message when it returns a different result

[hugocaillard]

Note that all of the clarity-wasm transactions are made from an other address than the default deployer.
It can lead to some weird behavior (like the funds of each addresses can differ).
Make sure it's not to confusing or error prone

See #1266 (comment)