chore: align Renovate release age for the whole vite-plus group

The vite catalog entry is an npm alias for @voidzero-dev/vite-plus-core,
so it matches the preset's generic npm rule (3-day minimumReleaseAge,
Monday schedule) instead of the vite+ rule (0 days, any time). When both
0.2.8 packages were published together, only vite-plus was eligible, so
the grouped PR bumped one catalog entry and left the alias at 0.2.7.

Set minimumReleaseAge and schedule on the group rule so every
@voidzero-dev/vite-plus-* package follows the same policy as vite-plus.

Author: fengmk2

.github/renovate.json

@@ -9,10 +9,12 @@
       "addLabels": ["needs-bundle-rebuild"]
     },
     {
-      "description": "Group all Vite+ packages into a single PR; they are published together at the same version. vite-plus is the bundler, so its updates can change dist/ output.",
+      "description": "Group all Vite+ packages into a single PR; they are published together at the same version. vite-plus is the bundler, so its updates can change dist/ output. 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-plus",
       "matchPackageNames": ["vite-plus", "@voidzero-dev/vite-plus-*"],
-      "addLabels": ["needs-bundle-rebuild"]
+      "addLabels": ["needs-bundle-rebuild"],
+      "minimumReleaseAge": "0 days",
+      "schedule": ["at any time"]
     }
   ],
   "customManagers": [