Bump the frontend group in /frontend with 1 update

[dependabot]

Bumps the frontend group in /frontend with 1 update: pnpm.

Release notes

Sourced from pnpm's releases.

v8.11.0

Minor Changes

• (IMPORTANT) When the package tarballs aren't hosted on the same domain on which the registry (the server with the package metadata) is, the dependency keys in the lockfile should only contain /<pkg_name>@<pkg_version, not <domain>/<pkg_name>@<pkg_version>.

  This change is a fix to avoid the same package from being added to node_modules/.pnpm multiple times. The change to the lockfile is backward compatible, so previous versions of pnpm will work with the fixed lockfile.

  We recommend that all team members update pnpm in order to avoid repeated changes in the lockfile.

  Related PR: #7318.

Patch Changes

• pnpm add a-module-already-in-dev-deps will show a message to notice the user that the package was not moved to "dependencies" #926.
• The modules directory should not be removed if the registry configuration has changed.
• Fix missing auth tokens in registries with paths specified (e.g. //npm.pkg.github.com/pnpm). #5970 #2933

Our Gold Sponsors

... (truncated)

Commits

• 058edcf chore(release): 8.11.0
• 3db0db8 revert: "feat: use-experimental-npmjs-files-index option (#7177)"
• 23039a6 fix: missing auth token in registries with paths included (#7337)
• 45bdc79 fix: pnpm add a-module-already-in-dev-deps should show message that it wasn...
• a2bf6a0 feat: use-experimental-npmjs-files-index option (#7177)
• 2d8015b chore(deps): update
• b54e815 chore(release): libs
• b1fd38c fix: don't remove modules directory when registry configuration changes (#7322)
• cd4fcff fix: use the registry domain in the package ID, not the tarball domain (#7318)
• b39e8af fix(deps): update rename-overwrite
• See full diff in compare view

Dependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting @dependabot rebase.

---

Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

• @dependabot rebase will rebase this PR
• @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
• @dependabot merge will merge this PR after your CI passes on it
• @dependabot squash and merge will squash and merge this PR after your CI passes on it
• @dependabot cancel merge will cancel a previously requested merge and block automerging
• @dependabot reopen will reopen this PR if it is closed
• @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
• @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
• @dependabot ignore <dependency name> major version will close this group update PR and stop Dependabot creating any more for the specific dependency's major version (unless you unignore this specific dependency's major version or upgrade to it yourself)
• @dependabot ignore <dependency name> minor version will close this group update PR and stop Dependabot creating any more for the specific dependency's minor version (unless you unignore this specific dependency's minor version or upgrade to it yourself)
• @dependabot ignore <dependency name> will close this group update PR and stop Dependabot creating any more for the specific dependency (unless you unignore this specific dependency or upgrade to it yourself)
• @dependabot unignore <dependency name> will remove all of the ignore conditions of the specified dependency
• @dependabot unignore <dependency name> <ignore condition> will remove the ignore condition of the specified dependency and ignore conditions