fix: support for pnpm 11.0.0-rc.5 (#2812)

When we initially added support for 11.0.0-rc.0, we had to put in a
workaround in lockfile-test.bzl due to the way peer suffixes changed
unexpectedly: pnpm/pnpm#11272 This has now
been fixed in more recent release candidates, so we can drop that
workaround.

---

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

- Searched for relevant documentation and updated as needed: yes/no
- Breaking change (forces users to change their own code or config): no
- Suggested release notes appear below: no

### Test plan

- Covered by existing test cases

Author: acozzette

.aspect/workflows/config.yaml

@@ -170,7 +170,9 @@ tasks:
           bazel:
               flags: ['--test_tag_filters=-skip-on-bazel9']
           env:
-              USE_BAZEL_VERSION: '9.x'
+              # TODO: change this back to 9.x once this bug is fixed:
+              # https://github.com/bazelbuild/bazel/issues/29393
+              USE_BAZEL_VERSION: '9.0.2'
     - format:
           queue: aspect-medium
     - buildifier:

e2e/pnpm_lockfiles/lockfile-test.bzl

@@ -148,7 +148,7 @@ def lockfile_test(npm_link_all_packages, name = None):
             # Workaround for peer suffixes changing in pnpm 11. We may want to
             # revisit this depending on the outcome of:
             # https://github.com/pnpm/pnpm/issues/11272
-            ":.aspect_rules_js/node_modules/@scoped+c@file+..+projects+c_@scoped+b@%sprojects+b" % ("+" if lock_version == "v110" else ""),
+            ":.aspect_rules_js/node_modules/@scoped+c@file+..+projects+c_@scoped+b@projects+b",
             ":.aspect_rules_js/node_modules/@[email protected]",
 
             # file: 4.17.21.tgz tarbal