chore(renovate): use the shared Vite+ version mapping

AGENTS.md

@@ -103,7 +103,7 @@ Open a pull request. Release rules no file enforces:
   Renaming any of them breaks publishing until the npm setting matches.
 - Keep `effect` and every `@effect/*` package in [`package.json`](package.json)
   on one exact version. A newer shared runtime can break the pinned Effect. The
-  `effect` group in [`renovate.json`](renovate.json) moves them together.
+  shared preset inherited by [`renovate.json`](renovate.json) moves them together.
 - The build bundles `jpeg-js` with the patch in [`patches/`](https://github.com/putdotio/rokit/blob/main/patches),
   because npm consumers do not inherit pnpm patches. Drop it only when a pinned
   upstream release passes the partial-interval and early-end-marker

renovate.json

@@ -1,13 +1,4 @@
 {
   "$schema": "https://docs.renovatebot.com/renovate-schema.json",
-  "extends": ["github>putdotio/.github:renovate-config"],
-  "packageRules": [
-    {
-      "description": "Effect packages ship together and peer on the same effect version, so they move as one PR. Each member keeps its own release-age clock, and strict filtering would merge the members that aged first. Filtering none takes the latest of every member and holds automerge until all of them age",
-      "matchPackageNames": ["effect", "@effect/*"],
-      "matchUpdateTypes": ["patch", "minor", "major"],
-      "groupName": "effect",
-      "internalChecksFilter": "none"
-    }
-  ]
+  "extends": ["github>putdotio/.github:renovate-vite-plus"]
 }