test: litesvm 0.13.1 + sbpf v3 (validating removal of the sbpf pin)

[mikemaccana]

Validates whether the sbpf revision pin (merged in #86) can be removed by upgrading to the latest litesvm.

What this changes

• Workspace litesvm 0.11.0 → 0.13.1 (Agave 4.0).
• [patch.crates-io] points solana-kite at solanakite/kite-rust@litesvm-0.13, which relaxes solana-instruction to >=3.2 so it can coexist with litesvm 0.13.1's =3.2.0 pin. The crates.io release (solana-kite 0.3.0) requires solana-instruction ^3.3.0 and is the sole blocker to the upgrade; it enters the root workspace via finance/vault-strategy.
• checking-accounts/asm and create-account/asm now inherit litesvm from the workspace, so all four asm crates build against 0.13.1.
• Drops the sbpf --rev pin so sbpf HEAD emits SBPF v3 (0x03 OS-ABI).

What the CI result means

• Green → litesvm 0.13.1 loads sbpf's SBPF v3 output. The pin can be removed permanently; next step is a published solana-kite release so the [patch] can be dropped.
• Red on InvalidAccountData → 0.13.1's default (mainnet-beta) feature set does not enable SBPF v3 execution; the pin stays (or the asm tests must enable the feature explicitly via FeatureSet).

This is an experiment on the temporary branch, not intended to merge as-is (it depends on an unpublished solana-kite branch via [patch]).

[mikemaccana]

Closed by bot.