Computation limit exceeding errors are treated as internal errors

[SupunS]

Current Behavior

If the user exceeds the computation limit, it should be a user error. But currently it is treated as an internal error (and prints the go-stacktrace). e.g: #2679

Expected Behavior

Such errors should be treated as user errors

Steps To Reproduce

Run a transaction/code that exceeds the computation limit.

Environment

- Cadence version: latest/master
- Network: TN/MN

[bluesign]

There are many places this is happening, I think best to solve would be generate a list of errors from transaction results and fix them all in a single PR.

[SupunS]

Yeah, this needed to be done for all calls to FVM from cadence. Fixed in #2683.

The panicked errors were already handled, but the returned errors were not.