Skip checking of events order while processing due to incorrect `logIndex` in FEVM

[nikugogoi]

Part of Run with sushiswap subgraph

• FEVM returns incorrect logIndex in eth_getLogs response
  • Skip check of order using logIndex as unprocessed block is removed on restarts and reprocessed from start
  • For batch events processing, use pagination instead of using block.lastProcessedIndex (set using logIndex)
• Use json-bigint stringify in job-runner processBatchEvents method
• Set event signature in events processing for contracts watched after subgraph template create
• Handle null block in async caching of block size