fix: yarn peers

[snowystinger]

Closes #7909

I'm not sure why yarn didn't create warnings for us during install in our own project. I've added it as a constraint rule, so we'll know in the future if we violate this again.

I tested against the test repo listed in the original issue, I no longer get which I did get when using the starting state.

Some peer dependencies are incorrectly met by dependencies; run yarn explain peer-requirements for details.

upon yarn install and I checked the old pnp.cjs vs the new one, the line pointed out in the comment is now different and I think correct.

Steps to run against test repo:

1. in react spectrum, run ./scripts/verdaccio.sh
2. wait until Press a key to close server and cleanup is displayed
3. go to test repo

yarn cache clean
yarn config set unsafeHttpWhitelist localhost
yarn config set npmRegistryServer "http://localhost:4000"
yarn install

✅ Pull Request Checklist:

• Included link to corresponding React Spectrum GitHub Issue.
• Added/updated unit tests and storybook for this change (for new code or code which already has tests).
• Filled out test instructions.
• Updated documentation (if it already exists for this component).
• Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

[devongovett]

Doesn't yarn itself check these? How did you find them in the first place?

[snowystinger]

I thought yarn should catch these, but for some reason it didn't, I don't know why.

Found them through the issue that was opened against us and by running the command I listed in the description on their reproduction repo.

I'd like to get this fixed for the user and then spend some time figuring out if there is a bug in yarn, possibly upgrading to a newer version would fix it.

[LFDanLu]

Verified before and after with the test repo, confirmed the peer dep warning didn't come up when using this branch via verdaccio