feat(store-sync,store-indexer): sync from getLogs indexer endpoint

[holic]

No description provided.

[changeset-bot]

🦋 Changeset detected

Latest commit: 74921c7

The changes in this PR will be included in the next version bump.

This PR includes changesets to release 30 packages

Name	Type
@latticexyz/store-sync	Major
@latticexyz/common	Major
@latticexyz/store-indexer	Major
@latticexyz/dev-tools	Major
@latticexyz/block-logs-stream	Major
@latticexyz/cli	Major
@latticexyz/config	Major
@latticexyz/protocol-parser	Major
@latticexyz/store	Major
@latticexyz/world-modules	Major
@latticexyz/world	Major
@latticexyz/react	Major
@latticexyz/abi-ts	Major
create-mud	Major
@latticexyz/ecs-browser	Major
@latticexyz/faucet	Major
@latticexyz/gas-report	Major
@latticexyz/network	Major
@latticexyz/noise	Major
@latticexyz/phaserx	Major
@latticexyz/recs	Major
@latticexyz/schema-type	Major
@latticexyz/services	Major
@latticexyz/solecs	Major
solhint-config-mud	Major
solhint-plugin-mud	Major
@latticexyz/std-client	Major
@latticexyz/std-contracts	Major
@latticexyz/store-cache	Major
@latticexyz/utils	Major

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[alvrs]

for context, why do we have to order the result here?

[holic]

it was an attempt to fix the e2e tests having inconsistent results between rpc and indexer as far how data is populated, but ended up not being enough

I fixed the e2e test here and need to bring this commit over: 74611df

ultimately we lose some fidelity/ordering when hydrating from the indexer because everything is done at the block level, so records pulled from the DB within the same block may not be exactly the same order as records created from a list of logs from the RPC (mostly due to a lack of logIndex)

this isn't really an issue practically speaking, but felt like it would be nice to have some consistency between rpc and indexer in terms of data returned and its ordering

[alvrs]

do we still need the sorting now? unclear if it affects performance at all

[holic]

we should still prob order by block number, but maybe not others

I think these will still take advantage of the index, but will remove for now

[alvrs]

lgtm, only question i have is if we can skip the overhead of sorting if it doesn't solve a problem