feat: configure if bridge syncer require for bridgeAsset the real `from` field in order to avoid using a archive-node

[joanestebanr]

Feature Request

The bridge syncer use debug_traceTransaction in several cases:

• For bridgeEvent (type Asset): to get the From of the caller to the bridge contract
• For claims: For legacy events it's required, but new contracts provide DetailedClaimEvent that is not needed anymore

So the idea is set a new config parameter to indicate if it's require the From field for bridges.

Take in considenration:

• Add a configuration field in the BridgeSyncer, as you suggested, e.g. SYNC_FROM_IN_BRIDGES
• Make the field From nullable (to know whether it has been explicitly set or not), both in the database and in memory.
• The BridgeService should take this field into account (not sure whether it should fail on startup or handle it in some other way).
• If a database has ever been started with FROM=false, it should no longer be possible to start it with a process that requires it to be true.
• We could add a sanity check on the contracts, but that would not guarantee anything, since there might be old events in the history.