Secure bls_rewards_request endpoint

[Doy-lee]

Various fixes to ensure that bls_rewards_request sanitises all input and various bug fixes encountered during testing.

• Correctly parse out multiple contributors in the serviceNodes smart contract call
• Fix ethyl::hexStringToU64 failing on large leading 0 padded strings
• Fix off-by-one in removable nodes prevent nodes from being flushed from the service node list
• Add many more debug logs into the python script
• Update txout check, I believe there will be 0 coinbase transactions after switching to arbitrum HF so I've updated the checks in the ServiceNodeList.
• In rewards request, we aggregate all other nodes and ensure we exclude ourselves from the aggregation process
• Verify returned aggregate parameters from other nodes against our own local signature
• Explicitly use hashHex when we are hashing a hex blob that needs to be decoded into binary first before hashing
• Fix unit tests failing due to changed staking requirement when transitioning into Arbitrum
• Added foundation pool ABI/contract to the local devnet script

More unit tests are succeeding with this branch, there's one failing with the core fee burn which needs more investigation to figure out what is happening there.

The local-devnet python script does not work with this PR. It needs a small temporary patch to be applied. It's broken because when we transition into the Arbitrum hardfork, all the active addresses in the batching DB is still set to Oxen addresses. However the BLS rewards claim is an API designed around matching against Ethereum addresses. This causes the script to fail when trying to query/get rewards.

As denoted in the screenshot the DB contains Oxen addresses.

The small workaround required is the code in this patch which I've removed from this PR to keep the integration branch clean. https://github.com/oxen-io/oxen-core/pull/1677/commits/520980c0adb2182e4eb0ac3b6fc81df451657251 We require the migration code which will convert the stored addresses into Ethereum addresses.

This depends on https://github.com/oxen-io/oxen-encoding/pull/37 and https://github.com/oxen-io/oxen-core/pull/1675

[darcys22]

Awesome stuff,

So something is happening, we add a node in the local devnet though the ethereum add node interface. That new node is added to our service node list and its rewards address is an ethereum address.

However its balance is no longer being added to the batching database

[darcys22]

Actually looking at that image now the service node active = false should definitely be true

[darcys22]

Thatll be it,

contributed 100 oxen but staking requirement is 120

[Doy-lee]

Ah yes, some of the numbers have been changed around. I had to fix it on the unit test, should have realised that the script needs to be updated.