rework the endpoints used in paima to use pagination based on txs

[ecioppettini]

About

This is based on the work on #173. Mostly because the slotLimits code is re-used here in order to be able to test it with paima. Potentially the upper limit in the slot range could be removed, but it was simpler to keep it for now. This allows to replicate the current behavior by just consuming the entire range, but allows chunking and skipping empty slots.

Pagination is added to the following endpoints:

/asset/utxos
/projected-nft/range
/delegation/pool

The pagination code is the same as the transaction history endpoint, which is based in transactions. The main breaking change is that the output format is changed in order to group events by transaction. So if previously the endpoints were returning

[
  {
    txId: "tx1",
    block: "block1",
    ...dataFields1
  },
  {
    txId: "tx1",
    block: "block1",
    ...dataFields2
  }
]

Now the shape is instead:

[
  {
    txId: "tx1",
    block: "block1"
    payload: [ dataFields1, dataFields2 ]
  }
]

The reasoning for this is that otherwise you can skip the second event after seeing the first one and using that tx as the after parameter.

The only really annoying part about this is that using json_agg doesn't really play well with pgtyped, but it's the simpler way of implementing this, since grouping in js it's most likely not the best idea.

Note: I tested the projected nft endpoint only with fake data, since I didn't really have indexed that for it in my carp instance.

[SebastienGllmt]

This needs to be rebased now