refactor(tokens): use kit codecs for instruction data in Token-2022 and create-token examples

[amilz]

What changed

Instruction data in these example test suites was built with the borsh package. This swaps that for @solana/kit codecs (getStructEncoder + getU8Encoder, plus addEncoderSizePrefix(getUtf8Encoder(), getU32Encoder()) for the string fields in the create-token examples), so the examples rely on a single serialization library instead of two.

• borsh removed from dependencies in all nine packages (no borsh usage remains in any of them)
• Lockfiles regenerated with the repo-pinned pnpm@10.33.0
• Wire format is unchanged: kit's u32-length-prefixed UTF-8 string matches borsh's string

Follows the pattern established in #675.

Packages

• tokens/token-2022/default-account-state/native
• tokens/token-2022/mint-close-authority/native
• tokens/token-2022/mint-close-authority/pinocchio
• tokens/token-2022/non-transferable/native
• tokens/token-2022/non-transferable/pinocchio
• tokens/token-2022/transfer-fee/native
• tokens/token-2022/multiple-extensions/native
• tokens/create-token/native
• tokens/create-token/pinocchio

Test evidence

For each package: pnpm install, tsc --noEmit, and pnpm build-and-test (cargo build-sbf + mocha/LiteSVM). All nine pass.

PASS tokens/token-2022/default-account-state/native
PASS tokens/token-2022/mint-close-authority/native
PASS tokens/token-2022/mint-close-authority/pinocchio
PASS tokens/token-2022/non-transferable/native
PASS tokens/token-2022/non-transferable/pinocchio
PASS tokens/token-2022/transfer-fee/native
PASS tokens/token-2022/multiple-extensions/native
PASS tokens/create-token/native
PASS tokens/create-token/pinocchio

prettier --check is clean on every changed file.

Part of DEV-838

[linear]

DEV-838

[greptile-apps]

Greptile Summary

The PR replaces Borsh-based instruction-data serialization with equivalent @solana/kit codecs across nine create-token and Token-2022 examples.

• Removes the borsh dependency and corresponding lockfile entries.
• Encodes single-byte decimal arguments with Kit struct/u8 encoders.
• Encodes create-token strings as u32-length-prefixed UTF-8 fields.
• The serialization layouts align with the program-side Borsh and Pinocchio parsers, but the PR commit is unsigned.

Confidence Score: 4/5

The code changes appear behaviorally sound, but the unsigned commit must be replaced with a signed, verified commit before merging.

The new codecs preserve the existing instruction wire formats, while the sole PR commit reports no signature and therefore violates the repository's mandatory commit-verification policy.

Important Files Changed

Filename	Overview
tokens/create-token/native/tests/test.ts	Replaces Borsh serialization with a Kit encoder whose ordered, little-endian length-prefixed fields match the native program's instruction schema.
tokens/create-token/pinocchio/tests/test.ts	Uses the same compatible Kit wire format for the Pinocchio parser and preserves the instruction payload.
tokens/token-2022/mint-close-authority/native/tests/test.ts	Replaces the one-byte Borsh decimal payload with an equivalent single-u8 Kit struct encoding.
tokens/token-2022/mint-close-authority/pinocchio/tests/test.ts	Preserves the one-byte decimals payload expected by the Pinocchio instruction parser.
tokens/token-2022/default-account-state/native/tests/test.ts	Migrates the single-u8 instruction payload to an equivalent Kit encoder.
tokens/token-2022/multiple-extensions/native/tests/test.ts	Migrates the single-u8 instruction payload to an equivalent Kit encoder.
tokens/token-2022/non-transferable/native/tests/test.ts	Migrates the single-u8 instruction payload to an equivalent Kit encoder.
tokens/token-2022/non-transferable/pinocchio/tests/test.ts	Preserves the one-byte decimals payload expected by the Pinocchio parser.
tokens/token-2022/transfer-fee/native/tests/test.ts	Migrates the single-u8 instruction payload to an equivalent Kit encoder.

_{Reviews (1): Last reviewed commit: "refactor(tokens): use kit codecs for ins..." | Re-trigger Greptile}

[greptile-apps]

Unsigned commit violates policy

Commit feb93df76b435904addf167ef7a6aa90b93c3798 has no signature, so this PR does not satisfy the repository's requirement for signed, verified commits and must be re-signed before approval.

Context Used: Request changes if the commits are not signed (ver... (source)