chore: keep alpha releases on 0.x (downgrade minor changesets to patch)

[RuudBurger]

The alpha release PR (#111) bumped most packages to 1.0.0-alpha.0. That's not a real major: @plextv/react-lightning (and plugin-flexbox) have minor changesets, so they'd go 0.4.2 → 0.5.0, which falls outside the ^0.4.2 peer range every plugin/dependent declares. changesets treats an out-of-range peer bump as breaking for consumers and cascades a major onto all of them → 1.0.0.

To stay on 0.x, this downgrades the 9 minor changesets to patch. Everything then bumps within ^0.4.x (no out-of-range peer change, no major cascade). Verified locally with changeset version in pre mode:

• before: react-lightning 0.5.0-alpha.0, everything else 1.0.0-alpha.0
• after: all packages 0.4.3/0.4.4-alpha.0

Trade-off: a few genuinely feature-level changes now land as patch in the changelogs. For a pre-1.0 framework in active alpha churn that's fine, and it keeps 1.0.0 unspent until we actually mean it. Once this merges, the changesets action will regenerate #111 with the 0.4.x versions.