chore: sync pnpm engines version with packageManager (#39950)

The pnpm `engines` range was still `>= 11.0.0` while `packageManager` is
on pnpm 12. Raise it to match, and set Renovate's range strategy for it
to `bump`, because the default strategy leaves an already satisfied `>=`
range untouched.

package.json

@@ -3,7 +3,7 @@
   "packageManager": "pnpm@12.13.0",
   "engines": {
     "node": ">= 22.18.0",
-    "pnpm": ">= 11.0.0"
+    "pnpm": ">= 12.13.0"
   },
   "dependencies": {
     "@codemirror/autocomplete": "6.20.3",

renovate.json5

@@ -107,6 +107,11 @@
       "matchPackageNames": ["mcr.microsoft.com/**"],
       "minimumReleaseAgeBehaviour": "timestamp-optional", // registry has no release timestamps, https://github.com/renovatebot/renovate/issues/38656
     },
+    {
+      "matchDepTypes": ["engines"],
+      "matchDepNames": ["pnpm"],
+      "rangeStrategy": "bump", // keep in sync with packageManager
+    },
     {
       "matchManagers": ["gomod"],
       "matchDepNames": ["go"],