chore: have renovate hold PRs for 3 days after release (#4788)

Recent renovate PRs went red because freshly-published versions
weren't fully propagated on the npm registry / CDN. `minimumReleaseAge`
delays PRs until the version is at least three days old, and
`internalChecksFilter: "strict"` suppresses the PR entirely until
that window passes rather than opening it and blocking merge.

Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

Author: escapedcat

package.json

@@ -88,6 +88,8 @@
   "renovate": {
     "rangeStrategy": "update-lockfile",
     "rebaseWhen": "behind-base-branch",
+    "minimumReleaseAge": "3 days",
+    "internalChecksFilter": "strict",
     "ignorePaths": [
       "**/fixtures/**/package.json"
     ],