chore: group all Vite+ packages on one Renovate policy (#42)

The `vite` catalog entry is an npm alias for
`@voidzero-dev/vite-plus-core`, so it falls into the preset's generic
npm-packages group (3-day `minimumReleaseAge`, Monday schedule) while
`vite-plus` follows the vite+ rule (0 days, any time). Each Vite+
release then splits across two PRs with mismatched versions: #36 bumps
`vite-plus` to 0.2.8 and leaves the alias at 0.2.1, while #37 bumps the
alias to 0.2.7 and leaves `vite-plus` at 0.2.1.

Add a repo rule so `vite-plus` and `@voidzero-dev/vite-plus-*` share the
vite+ group and the same age and schedule.

After merging, a Renovate run should fold the alias bump into #36 and
drop it from #37.

Author: fengmk2

.github/renovate.json

@@ -1,4 +1,13 @@
 {
   "$schema": "https://docs.renovatebot.com/renovate-schema.json",
-  "extends": ["github>Boshen/renovate"]
+  "extends": ["github>Boshen/renovate"],
+  "packageRules": [
+    {
+      "description": "Group all Vite+ packages into a single PR; they are published together at the same version. minimumReleaseAge and schedule keep @voidzero-dev/vite-plus-* (the vite catalog alias) on the same policy as vite-plus; the preset's generic npm rule would otherwise hold the alias behind a 3-day age gate and a Monday schedule.",
+      "groupName": "vite+",
+      "matchPackageNames": ["vite-plus", "@voidzero-dev/vite-plus-*"],
+      "minimumReleaseAge": "0 days",
+      "schedule": ["at any time"]
+    }
+  ]
 }