chore: bump sei-config to v0.0.24 (seed P2P reachability)

[bdchatham]

Why this repo matters here

The sidecar's ConfigApplier is what calls seiconfig.ResolveIntent, so this module's sei-config version is what a seed node actually boots on — not the controller's. On v0.0.23 a seed resolved the baseDefaults loopback P2P bind and accepted zero external peers, silently: it boots clean and logs nothing. This bump is the step that makes seed config correct in a running cluster.

What v0.0.24 brings

From sei-config #43 / #44:

• seed binds network.p2p.listen_address to 0.0.0.0:26656
• seed caps max_packet_msg_payload_size at 102400, bounding PEX recv-path allocation
• a seed config with pex disabled now fails validation instead of hard-erroring in makeSeedNode at boot
• NodePortsForMode gains a seed arm; port names exported as constants

No sidecar code changes

config-apply is mode-agnostic by construction — it deserializes a ConfigIntent and calls ResolveIntent, with all per-mode knowledge living in sei-config. A new node mode therefore costs the sidecar nothing. The diff is go.mod/go.sum plus tests.

Tests

Two added at the boundary this bump exists to fix, rather than re-testing sei-config's own defaults:

• TestConfigApplier_SeedIsReachable — an applied seed config binds 0.0.0.0:26656 and has pex enabled, asserted after a real write/read round-trip through the applier
• TestConfigApplier_SeedWithoutPexRejected — a seed reaching the sidecar with network.p2p.pex=false fails the task, rather than writing a config seid rejects at startup. This exercises the new validation rule through the task handler, which is the last gate before seid boots.

go build ./..., go test ./..., go vet ./..., gofmt -s -l all clean.

Next in the chain

sei-k8s-controller bumps to v0.0.24 and adds the seed SeiNode mode.

🤖 Generated with Claude Code

[cursor]

PR Summary

Low Risk
Dependency-only bump with no sidecar logic changes; risk is limited to sei-config v0.0.24 behavior for seed resolution and validation.

Overview
Bumps github.com/sei-protocol/sei-config from v0.0.23 to v0.0.24 so seed nodes resolved by the sidecar ConfigApplier get correct P2P defaults (reachable listen bind, required PEX) and validation behavior from upstream—no changes to sidecar production code beyond the dependency.

Adds two config-apply integration tests at the sidecar boundary: TestConfigApplier_SeedIsReachable asserts an applied seed config uses tcp://0.0.0.0:26656 and has PEX enabled after write/read; TestConfigApplier_SeedWithoutPexRejected asserts a seed with network.p2p.pex=false fails the task instead of writing boot-breaking config.

^{Reviewed by Cursor Bugbot for commit 24ac0c7. Bugbot is set up for automated code reviews on this repo. Configure here.}