fix: card-game tutorial — match actual evo-sdk API

[thepastaclaw]

Adds a corrected version of the Card Game with Tokens tutorial that compiles against @dashevo/evo-sdk@3.1.0-dev.1.

This is the most complex tutorial, combining documents and tokens. All fixes from the car-sales and basic-token tutorials apply here.

Changes from original tutorial

API	Tutorial (broken)	Fixed
contracts.publish()	Simplified fields + tokens: [config]	DataContract with TokenConfiguration + identityKey + IdentitySigner
documents.create()	{ contractId, documentType, document: {...} }	{ document: new Document({...}), identityKey, signer }
documents.query()	contractId, documentType	dataContractId, documentTypeName
documents.transfer()	{ contractId, documentId, recipientId, privateKeyWif }	{ document: Document, recipientId: Identifier, identityKey, signer }
tokens.mint()	{ tokenId, amount, privateKeyWif }	{ dataContractId, tokenPosition, amount: bigint, identityKey, signer }
tokens.transfer()	{ tokenId, identityId, privateKeyWif }	{ dataContractId, tokenPosition, senderId, identityKey, signer }
doc.getData()	method	doc.properties
contract.getId()	method	contract.id

npx tsc --noEmit passes with zero errors.

Resolves #5

[thepastaclaw]

✅ Live Testnet Run — All Steps Passed

Ran the card game tutorial on testnet with identity HHjmkbcwqFzToaoyvQcP45JZro7PoczAv7Nii57uYPX1.

Contract: 2GntY9SSk9BT81LhLGiExxLY3Vzv5seHSjz2fvH9z8LC
Gem token: 4mAQSVhgP5aeVBASSRdKGXrCjzPW4qWpFMkBG1fvTUCy

Minting 100 Gems...
Minted!

Creating cards...
  Created: Flame Sprite
  Created: Tidal Guardian

Cards found: 2
  Flame Sprite - fire - ATK:15 DEF:10
  Tidal Guardian - water - ATK:10 DEF:20

Recording match...
Match recorded!
Rewarding winner with 10 Gems...
Rewarded!

Gem balance: 110 Gems

=== CARD GAME: ALL STEPS PASSED ===

Additional issues discovered during live testing

All issues from Car Sales (#6) and Basic Token (#7) apply here, plus:

1. Mixed security levels needed — Contract publish and document create/query work with HIGH key, but token mint/burn/transfer require CRITICAL. A real tutorial would need to demonstrate using different keys for different operation types.
2. deck document type omitted from test — The deck type references card IDs, which would need to be populated after card creation. The schema itself is valid but practical testing requires a multi-step workflow.
3. Document transfer not tested — Requires a second identity to transfer cards to. The API signature is confirmed correct from the type definitions (tested in car-sales replace flow).