chore(ops): bump dojo-utils to pick up idempotent deploy fix

[kariy]

Summary

Advance saya's dojo-utils git dep from 4a374ac6 to 9b64ea8d — the merge commit of dojoengine/dojo#3404, which fixes Deployer::deploy_via_udc to return the real contract address (not Felt::ZERO) on the already-deployed path.

Lockfile-only change; bin/ops/Cargo.toml already pins branch = "main".

Why

Before dojo#3404, running saya-ops core-contract deploy --salt X twice against the same L2 emitted contract_address: "0x0" in both text and JSON output on the second run — because dojo-utils was dropping the real address on the is_deployed == true branch. Downstream orchestration (docker-compose init containers, CI scripts) then wrote 0x0 into state files and the next step panicked.

After the fix, deploy is idempotent: same salt → same address → same JSON shape, whether the contract was just deployed or was deployed last week.

Verification

Against a local katana dev chain that had already been deployed against with salt 0x7ee:

# Before this bump
$ saya-ops core-contract ... --output json declare-and-deploy-tee-registry-mock --salt 0x7ee
{"command":"...","contract_address":"0x0","salt":"0x7ee","tx_hash":null,"deployed_block":null}

# After this bump
$ saya-ops core-contract ... --output json declare-and-deploy-tee-registry-mock --salt 0x7ee
{"command":"...","contract_address":"0x37189b1807f1358074b70b3dc8ab79167bbf72cff1296286052f6dfe31c8f15","salt":"0x7ee","tx_hash":null,"deployed_block":null}

Test plan

• cargo build -p saya-ops clean with bumped Cargo.lock
• Idempotent redeploy with existing salt returns the real address (manual check against katana dev)
• CI green

🤖 Generated with Claude Code