Optimize safe events indexer

[moisses89]

Closes #2181

Description

This PR reduce the number of queries used to process the SafeSetup and ProxyCreation events, taking the advantage of commonly this two events are together in the same transaction or close in a batch of blocks.
Is important to highlight if the first event is SafeSetup will be always together with a ProxyCreation event because is a result of call DeployProxy with initializer.

Benchmark

The following sctipt was used to compare the results between the previous implementation and the implementation of this PR.

        SafeMasterCopy("0x29fcB43b46531BcA003ddC8FCB67FFE91900C762").save()
        SafeMasterCopy("0x3E5c63644E683549055b9Be8653de26E0B4CD36E").save()
        addresses = set(SafeMasterCopy.objects.all().values_list("address", flat=True))
        indexer = SafeEventsIndexerProvider()

        start_block = 1799327
        relevant = indexer.find_relevant_elements(
            addresses, start_block, start_block + 100
        )
        start = time.time()
        indexer.process_elements(relevant)
        print(f"Total time for {len(relevant)} {time.time() - start}")

Also used the same chain and RPC in both chains.

Results

Previous implementation:

2024-08-23 08:51:03,575 [INFO] [MainProcess] SafeEventsIndexer: Found 9288 events from block-number=1799327 to block-number=1799427 for 2 addresses
2024-08-23 08:51:11,350 [INFO] [MainProcess] Opening connection to Redis
Total time for process decoded elements 47.67031955718994
Total time for 9288 55.48148560523987

Current implementation:

2024-08-23 08:47:00,677 [INFO] [MainProcess] SafeEventsIndexer: Found 9288 events from block-number=1799327 to block-number=1799427 for 2 addresses
2024-08-23 08:47:10,637 [INFO] [MainProcess] Opening connection to Redis
2024-08-23 08:47:11,468 [INFO] [MainProcess] Inserted 9288 internal_txs 
2024-08-23 08:47:11,468 [INFO] [MainProcess] Inserted 4644 internal_decoded_txs
Total time for process decoded elements 4.111443758010864
Total time for 9288 11.770971059799194

[moisses89]

The previous implementation always tried to remove the InternalTx generated from ProxyCreation just in case the ProxyCreation came first. https://github.com/safe-global/safe-transaction-service/blob/main/safe_transaction_service/history/indexers/safe_events_indexer.py#L366
In such case, because the ProxyCreation never comes later, the InternalTx generated by SafeSetup leaves without singleton (to) forever.
Maybe would be better try to get the Proxy InternalTx from database to insert the correct parameters of SafeSetup what do you think? @safe-global/core-api
In the current implementation the ProxyCreation is storing the singleton address in the to field of InternalTx, not sure if is completely right.

[Uxio0]

What happens if they are already inserted?

[moisses89]

Raise an exception.
Ignoring conflicts in such case would fix the issue, 5eeabd4

[moisses89]

@Uxio0 ignore_conflicts fail because InternalDecodedTx have relation with internal_tx, basically the ORM try to prevent lose data.
We can use instead of that update_conflicts, but I'm concerned because I just discovered that bulk_create does not call save, and in that case post_save will not be fired.
Will this affect our signals handle?

[Uxio0]

bulk_create does in case we inherit our BulkCreateMixin

[moisses89]

I did a workaround in case that would be a collision inserting the same instance, shouldn't be any common because the bulk create is in atomic section and we are checking if the contract were indexed, basically if the setup and proxyevent were correctly inserted, shouldn't reach the insert section if would be indexed again.