Bump @worldware/msg peer dependency to ^0.12.0

[jsahleen]

Update @worldware/msg-react so its declared dependency on @worldware/msg requires 0.12.0 (semver range ^0.12.0).

@worldware/msg@0.12.0 is published (release). The current ^0.11.0 peer/dev range does not include 0.12.x (0.x caret ranges only allow patch bumps).

User story

As a msg-react consumer (and as a maintainer), I want @worldware/msg-react to peer-depend on @worldware/msg@^0.12.0, so apps align with the current msg release and avoid resolving an older incompatible peer.

What to change

• package.json peerDependencies["@worldware/msg"] → ^0.12.0
• package.json devDependencies["@worldware/msg"] → ^0.12.0 (keep local/CI tooling on the same major/minor floor as the peer)
• Refresh package-lock.json via npm install so the lockfile resolves @worldware/msg@0.12.0 (or compatible)
• Update the install example in README.md from @worldware/msg@^0.11.0 to @worldware/msg@^0.12.0

Acceptance criteria

• Peer and dev ranges both declare ^0.12.0
• Lockfile installs a 0.12.x @worldware/msg
• README install example uses @worldware/msg@^0.12.0
• npm test, npx tsc --noEmit, and npm run build still pass

Out of scope

• API or component behavior changes unrelated to the dependency bump (msg 0.12.0 inherits unspecified message lang, dir, and dnt; existing MsgMessage already reads those attributes)
• Publishing a new msg-react release (unless release automation already covers it on merge to main)

[github-actions]

🎉 This issue has been resolved in version 1.1.3 🎉

The release is available on:

• npm package (@latest dist-tag)
• GitHub release

Your semantic-release bot 📦🚀