Update pnpm to v9.12.3

[openverse-bot]

This PR contains the following updates:

Package	Type	Update	Change
pnpm (source)	packageManager	patch	9.12.2 -> 9.12.3

---

Release Notes

pnpm/pnpm (pnpm)

### [`v9.12.3`](https://redirect.github.com/pnpm/pnpm/blob/HEAD/pnpm/CHANGELOG.md#9123) [Compare Source](https://redirect.github.com/pnpm/pnpm/compare/v9.12.2...v9.12.3) ##### Patch Changes - Don't purge `node_modules`, when typing "n" in the prompt that asks whether to remove `node_modules` before installation [#​8655](https://redirect.github.com/pnpm/pnpm/pull/8655). - Fix a bug causing pnpm to infinitely spawn itself when `manage-package-manager-versions=true` is set and the `.tools` directory is corrupt. - Use `crypto.hash`, when available, for improved performance [#​8629](https://redirect.github.com/pnpm/pnpm/pull/8629). - Fixed a race condition in temporary file creation in the store by including worker thread ID in filename. Previously, multiple worker threads could attempt to use the same temporary file. Temporary files now include both process ID and thread ID for uniqueness [#​8703](https://redirect.github.com/pnpm/pnpm/pull/8703). - All commands should read settings from the `package.json` at the root of the workspace [#​8667](https://redirect.github.com/pnpm/pnpm/issues/8667). - When `manage-package-manager-versions` is set to `true`, errors spawning a self-managed version of `pnpm` will now be shown (instead of being silent). - Pass the find command to npm, it is an alias for npm search

---

Configuration

📅 Schedule: Branch creation - "before 4am on the first day of the month" (UTC), Automerge - At any time (no schedule defined).

🚦 Automerge: Enabled.

♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• [ ] If you want to rebase/retry this PR, check this box

---

This PR has been generated by Renovate Bot.

[github-actions[bot]]

Latest k6 run output[^update]

     ✓ status was 200

     checks.........................: 100.00% ✓ 6400      ✗ 0   
     data_received..................: 1.5 GB  8.8 MB/s
     data_sent......................: 837 kB  4.9 kB/s
     http_req_blocked...............: avg=27.01µs  min=1.94µs   med=3.67µs   max=20.9ms  p(90)=5.17µs   p(95)=5.59µs  
     http_req_connecting............: avg=18.74µs  min=0s       med=0s       max=12.48ms p(90)=0s       p(95)=0s      
     http_req_duration..............: avg=592.09ms min=40.26ms  med=514.51ms max=2.35s   p(90)=1.06s    p(95)=1.16s   
       { expected_response:true }...: avg=592.09ms min=40.26ms  med=514.51ms max=2.35s   p(90)=1.06s    p(95)=1.16s   
   ✓ http_req_failed................: 0.00%   ✓ 0         ✗ 6400
     http_req_receiving.............: avg=141.85µs min=43.4µs   med=107.43µs max=20.78ms p(90)=173.53µs p(95)=213.32µs
     http_req_sending...............: avg=21.19µs  min=6.89µs   med=18.72µs  max=5.34ms  p(90)=24.53µs  p(95)=26.92µs 
     http_req_tls_handshaking.......: avg=0s       min=0s       med=0s       max=0s      p(90)=0s       p(95)=0s      
     http_req_waiting...............: avg=591.93ms min=40.03ms  med=514.39ms max=2.35s   p(90)=1.06s    p(95)=1.16s   
     http_reqs......................: 6400    37.610313/s
     iteration_duration.............: avg=3.16s    min=761.83ms med=2.6s     max=8.28s   p(90)=6.22s    p(95)=6.51s   
     iterations.....................: 1200    7.051934/s
     vus............................: 4       min=4       max=30
     vus_max........................: 30      min=30      max=30

[^update]: This comment will automatically update with new output each time k6 runs for this PR