examples/brazilian-ecommerce and examples/latam-commerce-smoke pin stale @codespar/sdk versions

[dangazineu]

Problem

Two examples carry stale @codespar/sdk pins:

• examples/brazilian-ecommerce/package.json → "@codespar/sdk": "^0.6.0"
• examples/latam-commerce-smoke/package.json → "@codespar/sdk": "^0.3.0"

Every other example (pix-nfse-skeleton, nfse-from-natural-language, whatsapp-installment-negotiation) is on ^0.9.0. With the SDK now past 0.9, the caret on 0.6 / 0.3 won't pick up the current release at install time — a fresh npm install in these directories resolves an old, materially different SDK.

Fix

Bump both to "@codespar/sdk": "^0.9.0" (matching the rest of the examples). Regenerate package-lock.json in each directory (rm package-lock.json && npm install). Verify with npm run validate (and npm run validate:live if the example has one).

If either example doesn't build cleanly against ^0.9.0 because the SDK surface drifted between 0.3/0.6 and 0.9, that's a real surface-drift signal — fix the example to match the current SDK rather than holding back the pin. Note in the PR what changed.

Out of scope

• MCP package pin conventions (caret vs exact). Tracked separately as a policy decision.
• Touching any package under packages/.

Acceptance

• Both package.json files updated.
• Both package-lock.json files regenerated.
• Both examples pass npm run validate after the bump.