fix: revert mosaic to 0.0.22 alpha + republish macp

Two errors shipped in #419 (mosaic-v0.1.0 release):

1. Version policy violation — @mosaicstack/mosaic was bumped 0.0.21 →
   0.1.0, jumping out of 0.0.x alpha without authorization. The project
   stays in 0.0.x until GA. Revert to 0.0.22.

2. @mosaicstack/macp exports fix never reached the registry. PR #415
   fixed packages/macp/package.json exports.default (was pointing at
   ./src/index.ts, broke installed consumers with ERR_MODULE_NOT_FOUND),
   but did not bump macp's version. The post-merge publish workflow
   silently skipped macp@0.0.2 as "already published", leaving the bad
   copy on the registry. Installing mosaic@0.1.0 resolves macp@0.0.2
   from the registry and crashes on startup. Bump macp 0.0.2 → 0.0.3 to
   force republish with the correct exports map.

Follow-up cleanup after merge:
- delete git tag mosaic-v0.1.0 + Gitea release
- delete @mosaicstack/mosaic@0.1.0 from Gitea npm registry so `latest`
  reverts to the highest remaining version
- create new tag mosaic-v0.0.22 + Gitea release

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

packages/macp/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mosaicstack/macp",
-  "version": "0.0.2",
+  "version": "0.0.3",
   "repository": {
     "type": "git",
     "url": "https://git.mosaicstack.dev/mosaicstack/mosaic-stack.git",

packages/mosaic/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@mosaicstack/mosaic",
-  "version": "0.1.0",
+  "version": "0.0.22",
   "repository": {
     "type": "git",
     "url": "https://git.mosaicstack.dev/mosaicstack/mosaic-stack.git",