Update snarkVM version to 4.11.0 and bump devnode to 0.3.0

[iamalwaysuncomfortable]

Motivation

Bump snarkVM from 4.10.0 to 4.11.0 and release devnode 0.3.0.

The upstream diff between 4.10.0 and 4.11.0 is small and contained to the consensus version table and Varuna internals:

• Adds ConsensusVersion::V22 (test height 25). Mainnet schedules V21 at height 22,437,000 (target October 1, 2026, 21:00 UTC); testnet V21/V22 remain unscheduled.
• V21 now activates Varuna V3. V3 changes only the Fiat-Shamir domain separator and verifier plumbing; the serialized proof layout is identical to V2.
• snark.verify / snark.verify.batch finalize instructions now enforce the Varuna version against block height (V3 required at or after V21).

No ledger, store, or REST-facing APIs changed. Because the devnode boots at the latest test height it now runs under V22 / Varuna V3, but dev_skip_checks + test_consensus_heights still short-circuits execution, fee, and deployment proof verification before the Varuna version is consulted, so the placeholder-proof flow is unaffected.

Note for devnode users: programs calling snark.verify must now pass Varuna version 3, since the node runs at V22.

Test Plan

• cargo build --locked --all-targets: clean, no warnings.
• cargo fmt --all -- --check: clean.
• cargo test --locked: 6 unit tests and 6 integration tests pass.
• Updated the unit test asserting the latest test consensus version (V21 @ 24 -> V22 @ 25).

Related PRs

• Update snarkVM version to 4.10.0 #36 (snarkVM 4.10.0 bump)