fix(build): generate bindings for git dependencies

[BitHighlander]

Summary

• generate JavaScript and TypeScript bindings during the package prepare lifecycle
• make exact Git-SHA dependencies consumable without a published fork package
• make Protocol CI assert that a normal npm install creates the required bindings

Root cause

The staging SOP requires hdwallet to resolve the exact canonical device-protocol Git commit. A clean Yarn Git dependency install of the current staging SHA produced only lib/.keep because the repository had no prepare lifecycle. That made the Git pin unusable and forced consumers back to a separately published artifact.

Validation

• fresh node:20-bookworm container: npm ci generated all bindings through prepare
• exact GitHub commit installed through Yarn in a scratch consumer
• installed messages, Solana, and Zcash bindings are present
• Ironwood fields 19/20 and boolean serialization round-trip from the installed Git dependency

No protobuf wire definitions change. No package publish is involved.