chore(deps): standardize litesvm to 0.8.0 across basics/

[NikkiAung]

Summary

• Problem: litesvm was pinned to three different versions across basics/: ^0.3.3 (2 packages), ^0.4.0 (13 packages), and 0.8.0 (1 package — already pinned in add pinocchio transfer-tokens example #596)
• Root cause of the scatter: packages were added at different points in time with no consolidation pass
• Why not 1.x? litesvm 1.0.0 switched its entire API from @solana/web3.js (v1 types) to @solana/kit (web3.js v2). All existing test files import PublicKey, Transaction, TransactionInstruction from @solana/web3.js, so a 1.x bump would be a breaking web3.js v2 migration — not a simple version bump
• Fix: pin all 15 packages to 0.8.0 — the highest web3.js v1 compatible release — matching what basics/cross-program-invocation/native already uses

Changes

• 15 × package.json: litesvm version → 0.8.0 (no other changes)
• 15 × pnpm-lock.yaml: regenerated

0.8.0 vs 0.3.3 / 0.4.0 compatibility

0.8.0 is fully backward-compatible with the ^0.3.3 and ^0.4.0 API surfaces used in the existing tests (airdrop, addProgramFromFile, sendTransaction, getAccount all accept the same PublicKey/Transaction types). It adds new sysvar helpers and warpToSlot but removes nothing.

[greptile-apps]

Greptile Summary

This PR standardizes LiteSVM across the affected basics/ packages. The main changes are:

• Pins LiteSVM to version 0.8.0 in 15 package manifests.
• Regenerates the corresponding pnpm lockfiles.
• Records platform-specific native packages for macOS and Linux.
• Restores glibc and musl selectors for Linux native packages.

Confidence Score: 5/5

This looks safe to merge.

• The regenerated metadata now distinguishes glibc and musl binaries for both Linux architectures.
• No blocking issue remains in the updated dependency files.

Important Files Changed

Filename	Overview
basics/account-data/anchor/package.json	Pins LiteSVM to version 0.8.0.
basics/account-data/anchor/pnpm-lock.yaml	Locks LiteSVM 0.8.0 and includes explicit glibc and musl selectors for Linux binaries.
basics/account-data/pinocchio/pnpm-lock.yaml	Regenerates the LiteSVM 0.8.0 dependency graph with platform-specific native package metadata.

_{Reviews (2): Last reviewed commit: "fix: regenerate lockfiles with pnpm@10.3..." | Re-trigger Greptile}

[greptile-apps]

Linux Libc Selection Is Ambiguous

The regenerated entries remove the libc selectors from both GNU and musl LiteSVM binaries. On Alpine or another musl-based environment, pnpm can treat both Linux variants as eligible and install the incompatible GNU binary, causing LiteSVM to fail when the tests load its native module; preserve libc-specific package metadata or confirm the published 0.8.0 packages provide equivalent filtering.

[NikkiAung]

The regenerated entries remove the libc selectors from both GNU and musl LiteSVM binaries.

This is a pnpm 10 format change, not a regression introduced by this PR. The libc field is no longer stored in the lockfile resolution metadata under pnpm v10 — pnpm reads it directly from each optional package's own package.json at install time, so the selection still works correctly.

Crucially, basics/cross-program-invocation/native was already pinned to 0.8.0 and its lockfile (committed and merged to main) has the same format — no libc selector in the resolution entries:

litesvm-linux-x64-gnu@0.8.0:
  resolution: {integrity: sha512-...}
  engines: {node: '>= 20'}
  cpu: [x64]
  os: [linux]
  # no libc: field — same as all the new lockfiles in this PR

So the lockfile format here is consistent with what's already in main. CI runs on ubuntu-latest (glibc), which works fine in both the existing and new lockfiles.