Add support for evmconnect's "execution reverted" error code

[awrichar]

When querying network version, look for the unique error codes returned by either ethconnect or evmconnect.

Partial fix for #1245
Depends on hyperledger/firefly-evmconnect#67

[codecov-commenter]

Codecov Report

Merging #1249 (c4d7c22) into main (a7226c9) will not change coverage.
The diff coverage is 100.00%.

@@           Coverage Diff           @@
##             main    #1249   +/-   ##
=======================================
  Coverage   99.97%   99.97%           
=======================================
  Files         308      308           
  Lines       20555    20555           
=======================================
  Hits        20549    20549           
  Misses          4        4           
  Partials        2        2           

Impacted Files	Coverage Δ
internal/blockchain/ethereum/ethereum.go	100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

[awrichar]

Looks like another instance of unit test failure/race condition as noted in #1250

Also some unexplained E2E failures... They passed locally, so it feels like this may be yet another intermittent issue.

[nguyer]

Leaving my approval, with the assumption that test issues will get resolved.

[awrichar]

The failing E2E tests seem to be getting a "success" receipt for operations and then later setting them back to "pending".

From container-logs-TestEthereumMultipartyE2ESuite--evmconnect-postgres-erc20_erc721.zip:

�[34mfirefly_core_0_1  |�[0m [2023-04-03T19:07:12.798Z]  INFO Executing blockchain_pin_batch operation 3d50e255-8a76-4f0b-90e7-a8057742d03a via handler MultipartyManager d=pinned_private ns=default opcache=gHUVhbnP p=did:firefly:org/org_2c04ae|0x7687f51f767037399c2d293808601db9... pid=1 role=batchmgr
�[34mfirefly_core_0_1  |�[0m [2023-04-03T19:07:12.814Z]  INFO Received operation update: status=Succeeded request=default:3d50e255-8a76-4f0b-90e7-a8057742d03a message= pid=1 proto=fftokens role=event-loop
�[34mfirefly_core_0_1  |�[0m [2023-04-03T19:07:12.814Z] DEBUG fftokens updating operation default:3d50e255-8a76-4f0b-90e7-a8057742d03a status=Succeeded ns=default pid=1
�[34mfirefly_core_0_1  |�[0m [2023-04-03T19:07:12.814Z]  INFO Received operation update: status=Succeeded request=default:3d50e255-8a76-4f0b-90e7-a8057742d03a tx=0x7b249c2f47faec3ae604cec512815da8dbed834801c26bf3432e30e66da7e748 message= pid=1 proto=ethereum role=event-loop
�[34mfirefly_core_0_1  |�[0m [2023-04-03T19:07:12.815Z] DEBUG ethereum updating operation default:3d50e255-8a76-4f0b-90e7-a8057742d03a status=Succeeded ns=default pid=1
�[34mfirefly_core_0_1  |�[0m [2023-04-03T19:07:12.817Z] DEBUG ethereum updating operation default:3d50e255-8a76-4f0b-90e7-a8057742d03a status=Pending ns=default pid=1
�[34mfirefly_core_0_1  |�[0m [2023-04-03T19:07:12.818Z] DEBUG Operation update 'default:3d50e255-8a76-4f0b-90e7-a8057742d03a' from 'fftokens' ignored, as it does not match operation source 'ethereum' dbtx=6ou1vsUv ns=default pid=1

[awrichar]

E2E failures seem to be persistent. Opened #1256.