Upgrade @parity/product-sdk and dependencies to the latest releases

[UtkarshBhardwaj007]

Summary

Bring the @parity/product-sdk packages up to the latest releases. This repo is the furthest behind, so the upgrade is substantial.

Current versions

• @parity/product-sdk-host ^0.8.0
• @parity/product-sdk-signer ^0.6.3

Target versions (latest)

• @parity/product-sdk-host 0.14.1
• @parity/product-sdk-signer 0.11.1
• Add and pin the other @parity/product-sdk-* packages the quests use (chain-client 0.9.1, contracts 0.9.2, descriptors 0.8.0, tx 0.3.2) as needed.

Breaking changes to plan for

• The host and signer API surfaces changed across many minor releases between 0.8 and 0.14.
• @parity/product-sdk@0.18.0 introduced the Result based error API, replacing throws in submitAndWatch, contract .tx / .prepare, and cloud storage queryJson.

Because of the size of the jump, do this in steps and lean on the truAPI transport switch that this upgrade depends on.

What needs to happen

• Step the host and signer up to the target versions, resolving breaking changes at each stage.
• Adopt the Result error API across the quest code.
• Bump polkadot-api and the transitive @polkadot-api/* packages.
• Re-run every quest end to end.

Acceptance criteria

• The tutorial builds and typechecks on the new versions.
• Every quest completes against the host.
• Any tutorial smoke test passes.

[illegalcall]

Can i get assigned to it @UtkarshBhardwaj007 ?

[illegalcall]

PR #23 (opened for #20) already brings this repo to the targets listed here: host 0.14.1 and signer 0.11.1, single @parity/truapi instance, build and typecheck green. Those are the only product-sdk packages this repo commits.

On the other checklist items: the quest packages (chain-client, contracts, descriptors, tx) are installed by players at @latest during the levels, and the level docs explicitly say not to pin them, so pinning them here would contradict the docs. polkadot-api is transitive-only in this repo and moved with the host/signer bump. Happy to add pins if you'd rather have them; otherwise I think #23 closes this one too, pending the quest run-through.