optimize chainhook event ingestion

[rafaelcr]

There are a couple things we could do on the API side to optimize the ingestion of Chainhook events:

• Out of order requests: we can definitely do this, we'd just need to be careful not to consume a block that wants to transfer an inscription that hasn't been ingested in its genesis yet (we could also just accept the transfers and fill the genesis later but that would take some changes to do)
• In-order requests but using a queue: we could store the raw JSON payloads in a temp table API side as soon as they come, and keep a queue of events so we can process more of them in parallel. This would have similar constraints as the out of order requests but would allow us to manage memory, concurrency, etc. on the node.js side