feat: more than one block range for a contract

[typedarray]

Problem / use case

Sometimes, it's useful to skip certain block ranges when indexing a contract. For example, the Hyperliquid testnet appears to have some block ranges where the RPC does not work.

Currently you can only pass startBlock and endBlock.

Proposed solution

We could replace startBlock and endBlock with a blocks field that supports multiple ranges. Also, this could be a good time to introduce tags like "latest" which would represent the latest block when the server starts up (very common for block intervals / cron).

Examples

Simple bounded range

-  startBlock: 1000,
-  endBlock: 2000,
+  blocks: [1000, 2000],

Multiple ranges

+  blocks: [[1000, 2000], [2050, "latest"]],

No endBlock (live indexing)

-  startBlock: 1000,
+  blocks: [1000, undefined],

Open questions

1. How should the (very common) case of endBlock: undefined look? Perhaps we could come up with a tag like "latest". Could be "live", "realtime", or "latest" if we use something else to mean "the latest block when the server started up".

[tk-o]

We could go with factory functions to describe numerical ranges:

• between(x, y)
• lt(x) & lte(x)
• gt(x) & gte(x)