Make it easier to debug indirect call type mismatches

[zebreus]

Currently, indirect call type mismatches result in a relatively generic error. It would be invaluable if we could print both the expected and the actual signature here. Also, the index in the function table we just tried to call.

RuntimeError: indirect call type mismatch
    at <unnamed> (<module>[119]:0xffffffff)
    at <unnamed> (<module>[114]:0xffffffff)
    at <unnamed> (<module>[111]:0xffffffff)
    at PyObject_Vectorcall (python.wasm[10471]:0xffffffff)
    at _PyEval_EvalFrameDefault (python.wasm[11945]:0xffffffff)
    at gen_send_ex2 (python.wasm[11912]:0xffffffff)
    at gen_iternext (python.wasm[11938]:0xffffffff)
    at coro_wrapper_iternext (python.wasm[11950]:0xffffffff)
    at _PyEval_EvalFrameDefault (python.wasm[11945]:0xffffffff)
    at gen_send_ex2 (python.wasm[11912]:0xffffffff)
    at PyGen_am_send (python.wasm[11946]:0xffffffff)

[zebreus]

I think the same applies to direct calls

[Arshia001]

On principle, I agree this would be a worthwhile feature to have.

I think the same applies to direct calls

A direct call can never cause a mismatch as long as your module is well-formed, valid WASM.