fix(pnpm): setting required pnpm to v9

[eikeland]

Why

set required pnpm version to 9.

Check off the following:

• Confirm that I checked changes to branch which I am merging into.

  • I have validated included files
  • My code does not generate new linting warnings
  • My PR is not a duplicate, check existing pr`s

• Confirm that the I have completed the self-review checklist.

• Confirm that my changes meet our code of conduct.

[changeset-bot]

⚠️ No Changeset found

Latest commit: d59cf9f

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[github-actions]

Coverage Report

Status	Category	Percentage	Covered / Total
🔵	Lines	11.25%	3459 / 30735
🔵	Statements	11.25%	3459 / 30735
🔵	Functions	11.02%	85 / 771
🔵	Branches	24.06%	207 / 860

File Coverage

No changed files found.

Generated in workflow #5751