feat(store): add experimental config resolve helper

[alvrs]

• Aims to solve one of the main pain points of our current config parser, which breaks on user types in some cases
• Note that this is just a temporary solution, we're still planning to refactor our config parsing from ground up in the medium term (see prototype new MUD config #1668 for context)

[changeset-bot]

🦋 Changeset detected

Latest commit: 5295bb2

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

This PR includes changesets to release 30 packages

Name	Type
@latticexyz/common	Major
@latticexyz/block-logs-stream	Major
@latticexyz/cli	Major
@latticexyz/config	Major
@latticexyz/dev-tools	Major
@latticexyz/protocol-parser	Major
@latticexyz/store-indexer	Major
@latticexyz/store-sync	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

[holic]

I remember trying to add as const to our default MUD configs (world config, store config) and it broke downstream types in weird ways. Hopefully we can just add this more specific as const to just the namespace without those downstream effects, but yeah, should aim to as const the whole config.

[alvrs]

yeah the arrays for e.g. enums currently complain if the whole config is as const

[holic]

Do we wanna add as const to the world/store namespaces here?

[holic]

since this function isn't being called by default as part of mudConfig, we could just not include config here since we'd have a reference to it already being part of the input and only return the resolved config (and then no need to worry about naming of _resolved)

[alvrs]

agreed, updated

[holic]

since this is internal/not recommended for external use, we could just not document this? 🙈

[alvrs]

we need a changeset to trigger a snapshot release, but since we also added mapObject here there will be a snapshot release anyway, so happy to remove this one

[holic]

🙏 thank youuuuu