make the indexer index blocks chronologically
Indeed, otherwise weird behavior can occur when serving realtime indexed data.
now that we have the download feature, we can catch up on past contract transactions. Let's go back to indexing in historical order.
That also has the benefit of fixing retries. Indeed, with the reverse chronological order, retries having an older creation date will go to the bottom of the queue and get retried after all new incoming transaction to deploy stop.
Finally, we also get the correct transaction order through the created_at column that now orders the same way as what's on the blockchain. Unlike reverse chronological order which didn't have this property making it very hard to reindex in the proper order.
We could keep the reverse chronological order in a separate method/management command though.