`panic: validator InitGenesis` ... when upgrading stride to v26.0.3

After a, presumably, successful liquid staking of tokens on `stride`, we receive:

```sh
Liquid Staking Response : { stToken: { denom: '', amount: '' } }
```

which is what is expected in the `v9.2.1`. However, this should be resolved in the newer versions of `stride`: https://github.com/Stride-Labs/stride/blob/f9307f7012f4111678a4c6fa4d50f6ae638f4005/proto/stride/stakeibc/tx.proto#L85-L90

But when `stride` version is switched in `config.yaml` by, for example, add the following:
```
image: ghcr.io/cosmology-tech/starship/stride:v12.0.0
```
we run into errors. Specifically for all versions `>v17.0.0` to `v26.0.3`, we get `panic: validator InitGenesis updates already set by a previous module`.

### Detailed Logs:

https://gist.github.com/amessbee/3318d0532241633a5e0a17028d627465

### To Reproduce:

Use the following config file to start starship, and see the above mentioned error in logs for `stridelocal-genesis-0 ` container:

```sh
name: starship-localnet
version: 1.3.0

chains:
- id: cosmoshublocal
name: cosmoshub
numValidators: 1
faucet:
enabled: true
type: starship
ports:
rest: 1315
rpc: 26654
grpc: 9000
faucet: 8088
- id: stridelocal
name: stride
image: mudassirshabbir/stride:v26.0.3
numValidators: 1
ics:
enabled: true
provider: cosmoshublocal
faucet:
enabled: true
type: starship
ports:
rest: 1313
rpc: 26653
grpc: 9099
faucet: 8089
assets:
- base: ustrd
description: "The native token of Stride Network."
name: Stride
display: strd
symbol: STRD
logo_URIs:
png: "https://raw.githubusercontent.com/cosmos/chain-registry/master/stride/images/strd.png"
denom_units:
- denom: ustrd
exponent: 0
- denom: strd
exponent: 6
- base: stuatom
description: "The LSD token of Atom on Stride Network."
name: "Stride Staked ATOM"
display: statom
symbol: stATOM
logo_URIs:
png: "https://raw.githubusercontent.com/cosmos/chain-registry/master/stride/images/statom.png"
svg: "https://raw.githubusercontent.com/cosmos/chain-registry/master/stride/images/statom.svg"
coingecko_id: stride-staked-atom
denom_units:
- denom: stuatom
exponent: 0
- denom: statom
exponent: 6

relayers:
- name: stride-cosmoshub
type: go-relayer
replicas: 1
chains:
- cosmoshublocal
- stridelocal
ics:
enabled: true
consumer: stridelocal
provider: cosmoshublocal

explorer:
enabled: false

registry:
enabled: true
ports:
rest: 8081
```

Start with the provided config.yaml and the detailed logs for the stridelocal-genesis-0 container. Reproduce the failure using the Stride v26.0.3 image and compare behavior with the listed older versions. Done means the configured Stride chain starts without the "validator InitGenesis updates already set" panic and the reported setup can be tested.

Written by the indexing model from the issue text.