Fix contract tooling and storage migrations

[Rickyy1017]

Summary

Fix argument encoding for contract invocations, initialize contracts from deployment targets, generate distributable TypeScript bindings, and add explicit versioned migrations after WASM upgrades.

Related issues

Closes #455
Closes #456
Closes #457
Closes #458

Changes

• Add validated bytes32:, bool:, and some-i128: argument forms to scripts/invoke.mjs, with parser tests.
• Chain initialize after each Makefile deploy target, require the admin/oracle/treasury/fee settings, and print the initialized contract ID.
• Add a make bindings target and CI generation/upload of TypeScript clients; attach the bindings archive to published releases.
• Keep upgrade() from writing the version compiled into the old WASM. Add admin-only, idempotent migrate(from_version) entrypoints and v1-to-v2 migration tests for all contracts.
• Align the pinned Rust toolchain with the workspace's declared Rust 1.95 minimum.

Test plan

• Existing tests pass (make test) — not run per request.
• New tests added for changed behaviour (not executed).
• Manually verified against a local node / testnet — not run.
• npm test — not run per request.
• cargo fmt --all -- --check and cargo clippy --workspace --all-targets --locked -- -D warnings — not run per request.

Checklist

• Branch is up to date with main.
• No debug / dead code left in.
• cargo fmt and cargo clippy are clean — not run per request.

[vercel]

@Rickyy1017 is attempting to deploy a commit to the chonilius' projects Team on Vercel.

A member of the Team first needs to authorize it.

[drips-wave]

@Rickyy1017 Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits