eth1_monitor: fix endianness when storing in DB.

With the `web3.py` v4->v5 change, the `log.amount` was now passed as
`bytes`, so there's a chance there's something wrong with the ABI.
(When `web3` v4 was being used, this type conversion was not needed.)

Plain conversion to `int` results is test errors: wrong amount, and
subsequently wrong data (local DB deposit data corrupted). This is
because the data obtained from the log / event object, as emitted
by the contract, is of different endianness.

To fix this and arising typing issues, instead use a "dead code"
function from `DepositLog` and a double-pass to first obtain/process
the logs (raw data), and then populate objects (with typing).

Author: veox

trinity/components/eth2/eth1_monitor/eth1_data_provider.py

@@ -119,10 +119,14 @@ def get_logs(self, block_number: BlockNumber) -> Tuple[DepositLog, ...]:
                 "topics": [self._deposit_event_topic],
             }
         )
-        parsed_logs = tuple(
-            self._deposit_contract.events.DepositEvent().processLog(log)['args']
+        processed_logs = tuple(
+            self._deposit_contract.events.DepositEvent().processLog(log)
             for log in logs
         )
+        parsed_logs = tuple(
+            DepositLog.from_contract_log_dict(log)
+            for log in processed_logs
+        )
         return parsed_logs
 
     def get_deposit_count(self, block_number: BlockNumber) -> bytes:

trinity/components/eth2/eth1_monitor/eth1_monitor.py

@@ -326,7 +326,7 @@ def _process_logs(
         self, logs: Sequence[DepositLog], block_number: BlockNumber
     ) -> None:
         """
-        Simply store the deposit data from the log, and increase the corresponding block's
+        Store deposit data from the log in database, and increase the corresponding block's
         `deposit_count`.
         """
         seq_deposit_data = tuple(