chore: bump sei-config v0.0.17 → v0.0.18

[bdchatham]

Picks up sei-config#25 — v1→v2 write mode migration for seid v6.5.

What changes:

• Default WriteMode is now memiavl_only (was cosmos_only)
• Nodes with v1 configs (cosmos_only, dual_write, split_write) are automatically migrated on startup via DefaultMigrations()

Why: The nightly seid image rejects cosmos_only with invalid state-commit.sc-write-mode "cosmos_only", crash-looping all 13 chaos scenario validators. This fix makes the sidecar emit memiavl_only for all new and migrated nodes.

All tests pass.

🤖 Generated with Claude Code

[cursor]

PR Summary

Medium Risk
Indirect but operationally significant: default and migrated state-commit write mode affects how nodes persist state at startup, though this PR only changes the dependency pin.

Overview
Bumps github.com/sei-protocol/sei-config from v0.0.17 to v0.0.18 (lockfile updates only in this repo).

That release aligns node config with seid v6.5: default state-commit.sc-write-mode becomes memiavl_only instead of cosmos_only, and legacy v1 modes are migrated on startup via DefaultMigrations(). Intended to stop validators from crash-looping when newer seid rejects cosmos_only.

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