docs: do not promise removal of .npmrc registry routing in rules_js 4 (#3093)

I think we should probably keep support for pnpm 10 in rules_js 4.0,
given that pnpm 10 is still officially supported until April 2027.

---

### Changes are visible to end-users: no

### Test plan

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
diff --git a/npm/private/npm_translate_lock.bzl b/npm/private/npm_translate_lock.bzl
index 5f1c83c..22b1c1f 100644
--- a/npm/private/npm_translate_lock.bzl
+++ b/npm/private/npm_translate_lock.bzl
@@ -223,7 +223,7 @@
 
             `@scope:registry` entries route scoped packages to their registry. With pnpm 11 and newer, declare
             registries with the `registries` setting of `pnpm-workspace.yaml` instead; routing from `.npmrc` is
-            kept for older pnpm versions and will be removed in rules_js 4.
+            kept for older pnpm versions and will be removed in a future major release.
 
             A [`tokenHelper`](https://pnpm.io/npmrc#urltokenhelper) is also honored: rules_js runs the executable it
             names and uses the token it prints on stdout. The helper path may be absolute or relative to this
diff --git a/npm/private/npm_translate_lock_state.bzl b/npm/private/npm_translate_lock_state.bzl
index 687112d..27411d6 100644
--- a/npm/private/npm_translate_lock_state.bzl
+++ b/npm/private/npm_translate_lock_state.bzl
@@ -380,7 +380,7 @@
 
     (registries, auth) = helpers.get_npm_auth(contents, npmrc_path, rctx)
 
-    # TODO(v4): drop `.npmrc` registry routing once pnpm < 11 support is dropped;
+    # TODO: drop `.npmrc` registry routing once pnpm < 11 support is dropped;
     # pnpm 11 declares registries in pnpm-workspace.yaml
     priv["npm_registries"].update(registries)
     priv["npm_auth"].update(auth)