fix(store-sync,store-indexer): make last updated block number not null

[holic]

following up #1965

not strictly a bug but just doing this for completeness so we don't have to sort inline

[changeset-bot]

🦋 Changeset detected

Latest commit: fe69511

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-indexer	Major
@latticexyz/store-sync	Major
@latticexyz/dev-tools	Major
@latticexyz/abi-ts	Major
@latticexyz/block-logs-stream	Major
@latticexyz/cli	Major
@latticexyz/common	Major
@latticexyz/config	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/protocol-parser	Major
@latticexyz/react	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/store	Major
@latticexyz/utils	Major
@latticexyz/world-modules	Major
@latticexyz/world	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

[holic]

originally had this as

.orderBy(sql`${tables.recordsTable.lastUpdatedBlockNumber} ASC NULLS FIRST`)

but then realize there's ~no case where we'd add records to the table without a block number (both RPC and another indexer will provide this info)

so I decided to make these fields not nullable