feat: raise virtual machine errors

[antazoey]

What I did

• Improved error handling around failed transactions.
• Handle when a transaction is reported as "failing"

How I did it

• Raise TransactionError from web3.py's ValueError (web3.py raises ValueError for different Virtual-machine related errors). Also raise when a transaciton is reported as failing.

How to verify it

when specifying a poor gas limit (too high, too low, etc), you should get TransactionErrors.

Like: ERROR: {'code': -32000, 'message': 'Transaction requires at least 63744 gas but got 1000'}
when the gas is too low (contract = test_account.deploy(contract_type, gas_limit=1000))

and ERROR: {'code': -32000, 'message': 'Transaction gas limit is 100000000 and exceeds block gas limit of 30000000'}
when the gas is too high (contract = test_account.deploy(contract_type, gas_limit=100000000))

Note: TransactionError ultimately will help us write the ape.test.reverts() fixture!

Checklist

• Passes all linting checks (pre-commit and CI jobs)
• New test cases have been added and are passing
• Documentation has been updated
• PR title follows Conventional Commit standard (will be automatically included in the changelog)

[antazoey]

Now, this method only returns errors instead of raising them.
If it returns None, we did not detect a transaction related error and the user of the method handle that however.

In our ape-http example, if we don't get a transaction error from this, we raise the original error.

[antazoey]

I have noticed an issue:

If estimating gas (not specifying a gas limit), and calling a transaction that will revert, the transaction fails at that point with the revert message, so that is why brownie must raise the VirtualMachineError then as well.

---

fixed

[antazoey]

We either have to do this, or any test that uses ape.reverts() will have to specify a gas_limit.

---

Edit:

Comment outdated, now says if isinstance(tx_error, VirtualMachineError):