test(integration): seed a genesis vesting fixture for the solo-precompile suite

[bdchatham]

Summary

Restores the solo-precompile locked-balance coverage that qa-testing#149 had to skip. TestNightlyRelease and TestNightlyGigaMixedRelease (solo.spec.ts runs in both) now derive a second identity and fund it in genesis with a continuous vesting schedule (1000000usei locked of a 2000000usei balance, unlocking to 2030) via the new SeiNetwork spec.genesis.accounts[].vesting field (from #496 / seictl v0.0.68), then hand its address + mnemonic to the release-test Job as SEI_VESTING_ADDRESS / SEI_VESTING_MNEMONIC (+ the unprefixed VESTING_ADDRESS alias) — mirroring the existing admin-identity pattern exactly.

This replaces the deprecated live seid tx vesting create-vesting-account the test used to build its fixture (sei-chain #3714 rejects it on nightly's chain-id).

Consumer

The qa-testing test that reads this fixture: sei-protocol/qa-testing tests/vesting-genesis-fixture (companion PR). That PR un-skips the test and consumes SEI_VESTING_MNEMONIC.

Merge + deploy ordering (important)

This PR builds against main (which has #496's SDK Vesting field + seictl v0.0.68). But the restored test only runs correctly once all of these are true at nightly time:

1. this PR merged → a new integration-harness image built,
2. the qa-testing companion PR merged → a new release-test image built,
3. the nightly sidecar image is built from seictl ≥ v0.0.68 (so the assembler honors vesting), and
4. the nightly cronjob's RELEASE_TEST_IMAGE (+ harness image) bumped to pick up 1–2.

Items 3–4 are platform/Flux changes tracked separately (steps 3 + 5 of the workstream).

xreview

Gated by a 4-lens xreview (kubernetes-specialist [dissenter], solidity-developer, security-specialist, idiomatic-reviewer) — RESOLVED, unanimous. Key-derivation parity (Go keygen ↔ cosmjs/CLI) verified airtight; the continuous schedule keeps ~999.9k of the 1 sei locked for the whole run; the solo Claim is all-or-nothing and reverts. One non-blocking follow-up filed: a run-time nonzero-locked guard (deferred — StartTime=genesis is confirmed in the assembler; the two load-bearing invariants are documented in the fixture comment).

Test plan

• go vet -tags integration ./test/integration/..., gofmt, golangci-lint --build-tags=integration clean on the diff
• Integration run (needs a live cluster + a ≥v0.0.68 sidecar) — validated at nightly once the deploy items above land

🤖 Generated with Claude Code

[cursor]

PR Summary

Low Risk
Changes are limited to integration test provisioning and K8s job env/secrets; no production controller or runtime behavior is modified.

Overview
Nightly integration (TestNightlyRelease and TestNightlyGigaMixedRelease) now seeds a second genesis account with a continuous vesting schedule so the external release-test harness can run solo-precompile locked-balance coverage without live MsgCreateVestingAccount.

The harness derives a vesting identity alongside the admin, provisions 2M usei with 1M usei locked until 2030 via sei.GenesisAccount.Vesting, and passes address + mnemonic into the release-test Job through a dedicated Secret and SEI_VESTING_* / VESTING_* env vars, mirroring the existing admin wiring. vestingFixture* constants and comments document the balance vs. locked invariants and the seictl StartTime dependency.

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