feat(settlement): added DRS version to MsgUpdateState

[keruch]

PR Standards

This PR implements https://www.notion.so/dymension/DRS-Vulnerability-Recovery-5b42195818264165aa72718e0e173f5b

Closes dymensionxyz/dymension#1207

---

For Author:

• Targeted PR against correct branch
• included the correct type prefix in the PR title
• Linked to Github issue with discussion and accepted design
• Targets only one github issue
• Wrote unit and integration tests
• All CI checks have passed
• Added relevant godoc comments

---

For Reviewer:

• confirmed the correct type prefix in the PR title
• Reviewers assigned
• confirmed all author checklist items have been addressed

---

After reviewer approval:

• In case targets main branch, PR should be squashed and merged.
• In case PR targets a release branch, PR should be rebased.

[mtsitrin]

@keruch where is this value validated across the L2?
what prevents the sequencer from lying?

[mtsitrin]

I see that each node validates his own version vs the rollapp params

if version.Commit != m.State.RollappParams.Version {
    return fmt.Errorf("binary version mismatch. rollapp param: %s binary used:%s", m.State.RollappParams.Version, version.Commit)
}

but I don't see where it's validated in regard with the state updates.

let's assume L2 runs version 8.
but the sequencer sets DrsVersion: 9 in the state update (e.g to bypass the DRS check)

[mtsitrin]

@danwt as discussed, this scenario should be fraud provable
pls link the related research/ADR/issue