chore: remove .yarnrc leftover

[dbrugger]

When looking into a solution for #14235, I saw carbon is on yarn v3 but still has a .yarnrc floating around. This file is now ignored according to https://yarnpkg.com/migration/guide#update-your-configuration-to-the-new-settings

Changelog

Removed

• .yarnrc

Testing / Reviewing

• test local development flow

[netlify]

✅ Deploy Preview for carbon-components-react ready!

Name	Link
🔨 Latest commit	7ecf515
🔍 Latest deploy log	https://app.netlify.com/sites/carbon-components-react/deploys/64e4dca319f50c0008810a36
😎 Deploy Preview	https://deploy-preview-14470--carbon-components-react.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[netlify]

✅ Deploy Preview for carbon-elements ready!

Name	Link
🔨 Latest commit	7ecf515
🔍 Latest deploy log	https://app.netlify.com/sites/carbon-elements/deploys/64e4dca31bf71a00083371f6
😎 Deploy Preview	https://deploy-preview-14470--carbon-elements.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify site configuration.

[tay1orjones]

My previous understanding of this was that we still needed this file because Netlify only formally supported yarn v1/classic. By incrementing the version in the .yarnrc we were sort of tricking Netlify into allowing our deploy previews to build.

Looking into it again though, I see netlify/build-image#779 has now been resolved but there are still a couple outstanding issues as it relates to yarn berry/v3

• Yarn 3 workspaces are not cached at all netlify/build-image#615
• Fix support for Yarn Plug'n Play in the plugins execution netlify/build#1535

The deploy previews did succeed on this PR, so that's a good sign.

@carbon-design-system/developers-system I think it's worth trying to merge this and if we have issues with Netlify deploy previews we may need additional config. Or we could roll back to put yarnrc back in.

[dbrugger]

i also find yarn versioning confusing. I recently updated one of our projects to v3, and it took a while for me to understand that yarn consists of two parts:

• the yarn cli on the system, which always is v1
• the yarn code in .yarn/releases which in this case is v3

on my system when I run yarn --version in the carbon repo, it shows 3.6.1. when I run it in ~, it shows 1.22.19.
Netlify will have the yarn cli, and use whatever is in .yarn/releases. I cannot imagine a true v1 being able to deal with that lock file format anyway.