EVM errors use inconsistent casing

[scorbajio]

eof errors have a different casing than the evm's own errors:

        // If value is nonzero and in static mode, throw:
        if (runState.interpreter.isStatic() && value !== BIGINT_0) {
          trap(ERROR.STATIC_STATE_CHANGE)
        }

        // If value > 0, charge CALL_VALUE_COST
        if (value > BIGINT_0) {
          gas += common.param('callValueTransferGas')
        }

        // Check if the target address > 20 bytes
        if (toAddr > EXTCALL_TARGET_MAX) {
          trap(EOFError.InvalidExtcallTarget)
        }

STATIC_STATE_CHANGE is snake case and InvalidExtcallTarget is camel case. It would be more consistent if they were the same casing.

[jochem-brouwer]

We should update the EOF errors to use the snake case format, so InvalidExtcallTarget -> INVALID_EXTCALL_TARGET and for the other errors as well 😄 👍