chore(deps): bump sei-config to v0.0.27 across all three modules

[bdchatham]

Bumps sei-config v0.0.25 → v0.0.27 in all three Go modules. Pins only; no source change.

Why

v0.0.27 carries chain.freeze_height (sei-config#49, released in sei-config#50). Until the pin moves, the sidecar's override resolution rejects the key as unknown, so a SeiNode cannot set a freeze height declaratively.

All three modules move together so the schema stays consistent across the controller, the sidecar that resolves overrides, and the shared API types.

One thing the diff does not show

v0.0.27 also adds network.p2p.accept_interval, defaulted to 10ms, which renders into config.toml [p2p] accept-interval for every node whose config-apply runs after the bump. Existing Running nodes are unaffected, because config-apply is init-only — the exposure is newly-bootstrapped nodes. Flagging it because "pins only" is true of the Go source, not of the rendered artifact.

Whether a 10 ms inbound accept interval is right for a seed under a handshake burst is a separate question; this PR does not change any value.

Testing

Check	Result
go build ./... in all three modules	pass
go test ./... in all three modules	pass
Full envtest suite	pass
go vet ./...	clean
gofmt -l .	clean
go mod tidy leaves no diff	pass

Consumed by

sei-protocol/sei-k8s-controller#NEXT stacks on this branch and adds the freeze sub-spec that uses the key. This PR is independently mergeable.

🤖 Generated with Claude Code

[cursor]

PR Summary

Medium Risk
Dependency-only PR, but the new sei-config defaults can change rendered node config.toml for new boots and enables upcoming freeze-height overrides that affect chain behavior.

Overview
Bumps github.com/sei-protocol/sei-config from v0.0.25 to v0.0.27 in the root controller, sidecar, and sidecarapi modules (go.mod / go.sum only). There are no Go source edits in this diff; behavior changes come from the upgraded library schema and templates.

The pin unlocks chain.freeze_height in override resolution (today v0.0.25 treats it as unknown), which a follow-up PR will use for declarative chain freeze. Keeping all three modules on the same version keeps config validation, sidecar config-apply, and shared ConfigIntent types aligned.

Side effect reviewers should know: v0.0.27 also introduces network.p2p.accept_interval (default 10ms), which will render into config.toml [p2p] accept-interval when config-apply runs on newly bootstrapped nodes—not on already-running pods where apply is init-only.

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