fix: return error for eth_call when call errors

[davidmurdoch]

fixes #1496

[MicaiahReid]

I've tested the change and it all looks good.

I do think this change gives further support for the idea of reversing --vmErrorsOnRPCResponse to something more like --suppressVmErrors, where the vm errors are enabled by default and can optionally be ignored.

It seems strange that the default use case would be that most vm errors are disabled, except for those from eth_call which are always enabled.

Then again, if that's what geth does that's what geth does.

[davidmurdoch]

Allowing users to do vmErrorsOnRPCResponse = false was so they can make ganache more like a real node, since when running a transaction real nodes don't throw on errors. This makes sense, because transactions aren't run immediately, but they are prioritized and only run when the miner chooses to put the transaction in a block -- and sometimes that can take days (or never).

eth_call is often used by developers to learn why a previously run transaction reverted. This PR makes that possible by default again.

Still +1 on picking a new name for this flag. Changing the default mode would also require changing the default for legacyInstamine to true, which doesn't make it very legacy any more. haha