Fix unsupported PNPM error message

[deivid-rodriguez]

What are you trying to accomplish?

Give good error messages.

Anything you want to highlight for special attention from reviewers?

PNPM 9 is now supported.

How will you know you've accomplished your goal?

New error reads properly.

Checklist

• I have run the complete test suite to ensure all tests and linters pass.
• I have thoroughly tested my code changes to ensure they work as expected, including adding additional tests for new functionality.
• I have written clear and descriptive commit messages.
• I have provided a detailed description of the changes in the pull request, including the problem it addresses, how it fixes the problem, and any relevant details about the implementation.
• I have ensured that the code is well-documented and easy to understand.

[jurre]

Hey hey 👋 what kinds of errors are you seeing currently @deivid-rodriguez ?

[deivid-rodriguez]

I'm not seeing any errors, I just saw this in the code base and noticed the message needed an update :)

I do suspect there's something not quite working with corepack version switching because I noticed that 176339f was already present before upgrading PNPM at #10073. So my understanding is that corepack should've been switching to PNPM 9 when finding an modern PNPM lockfile and not revert the lockfile format, even without #10073.

So I will dig a bit more into that, in case there's something else that needs fixing!