test: add litesvm ts testcases

[aarjn]

hy @Perelyn-sama raised PR here addressing the closed PR #392

Also I have noticed almost every ts test file for native program in basic are in bankrun.

[dev-jodee]

Can you fix the CI gh action failure

[greptile-apps]

Greptile Summary

This PR moves the native CPI TypeScript tests onto LiteSVM. The main changes are:

• Adds litesvm to the native CPI package dependencies.
• Builds the hand and lever SBF programs into test fixtures before running tests.
• Rewrites the CPI test to load fixture programs and send transactions through LiteSVM.

Confidence Score: 5/5

This looks safe to merge.

• No blocking issues found in the changed code.

Important Files Changed

Filename	Overview
basics/cross-program-invocation/native/tests/test.ts	Rewrites the CPI flow to use LiteSVM with Mocha tests and fixture-loaded programs.
basics/cross-program-invocation/native/package.json	Adds LiteSVM and updates the build-and-test script to build both native programs before tests run.
basics/cross-program-invocation/native/pnpm-lock.yaml	Locks LiteSVM and its platform-specific optional packages.

_{Reviews (2): Last reviewed commit: "test: add litesvm ts testcases" | Re-trigger Greptile}

[greptile-apps]

Mocha Sees No Tests

The package script still runs this file through ts-mocha, but these imports register suites with Node's node:test runner instead of Mocha. When pnpm test loads the file, Mocha can see an empty suite and report success without running the CPI transactions.

Suggested change

	import { before, describe, it } from "node:test";
	import { before, describe, it } from "mocha";

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Failure Details Are Masked

If sendTransaction returns its failed-transaction variant, this branch assumes that object has meta() and can throw a TypeError while building the error message. A real program error or funding failure would then lose the LiteSVM failure details and report the wrong exception.