Default GRAPH_GETH_ETH_CALL_ERRORS should be expanded to cover reth

[matthewdarwin]

Bug report from discord:

https://discord.com/channels/438038660412342282/859493040238755850/1471483734686433311
From: Tehn

QmT1c8d4YvkwdRzkqXEJ5Gps3bBGZGj4hQ86dy74bQw6Vx https://thegraph.com/explorer/subgraphs/FvBtepQuN5mwyHExX3GZodEKkzMtjkeKGJp1tznbx7Hn?view=Query&chain=arbitrum-one has graft QmePcrgbPJv2VBgUXv8QS6uvu1SWWtCwKUzcrKEwQssTm5 which fails
Ethereum node returned an error when calling function "decimals" of contract "ERC20": RPC error: Error { code: ServerError(-32003), message: "EVM error: InvalidJump", data: None }, block_hash: 0x05178b2b9f6794acc050e3c8c3cd20bc01c941b253964d51ac955dbf0a83d5a9, block_number: 24581599, runner_index: 75, sgd: 450, subgraph_id: QmePcrgbPJv2VBgUXv8QS6uvu1SWWtCwKUzcrKEwQssTm5, component: SubgraphInstanceManager

We are running different chain node clients and they return different code and message.
Geth: -32000 │ invalid jump destination
Reth/Erigon: -32003 │ EVM error: InvalidJump

I did research and found that graph node gracefully handle some geth messages (not code???), but do not understand reth/erigon.
invalid jump destination is in the GETH_EXECUTION_ERRORS , but not EVM error: InvalidJump

And in https://discord.com/channels/438038660412342282/859493040238755850/1471483067779514410
From: Marc-André | Ellipfra

are you using reth? Reth has different error codes for deterministic eth_call errors and require a custom mapping into graph-node. Here is my config:

- name: GRAPH_GETH_ETH_CALL_ERRORS
              value: "vm execution error;invalidjump;notactivated"