feat: automate upstream patch sync

[riderx]

Summary

• add a scheduled workflow that scans Capacitor+ sync/upstream-pr-* branches every 6 hours and opens patch catalog PRs
• add a patch sync runner that filters external Capacitor PRs, checks Capacitor+ branch status, generates package-root patches, and builds compiled artifacts for core/CLI/native bridge patches
• add a post-merge workflow that can comment quick-patch instructions on upstream Capacitor PRs when a PAT is configured
• document the recurring sync and manual DX

Validation

• bun run test
• bun run lint
• bun run verify
• bun run sync:patches -- --capacitor-plus-dir /Users/martindonadieu/Projects/capgo_all/capgo_plugins/capacitor-plus --remote capgo --base-ref capgo/plus --dry-run --no-require-checks --max-build-prs 0
• bun run sync:patches -- --capacitor-plus-dir /Users/martindonadieu/Projects/capgo_all/capgo_plugins/capacitor-plus --remote capgo --base-ref capgo/plus --pr 7598 --dry-run --no-require-checks --max-build-prs 1
• bun run sync:patches -- --capacitor-plus-dir /Users/martindonadieu/Projects/capgo_all/capgo_plugins/capacitor-plus --remote capgo --base-ref capgo/plus --pr 6991 --refresh-existing --dry-run --no-require-checks --max-build-prs 1
• git diff --check

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: b9dfcc07-ae53-4253-aa51-6b550ec01b80

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/auto-sync-upstream-patches

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[github-actions]

Beta npm build

Maintainers can publish this PR to npm for fast testing.

Comment /publish-beta after the PR checks are green.

The workflow will:

• publish a prerelease package on the beta tag
• add a pinned pr-1 dist-tag for this exact PR build
• update this comment with the install command

Security note: beta publish is only enabled for branches inside this repository.