[chore] Evaluate package managers for this project to use

[brandonlenz]

Is your feature request related to a problem? Please describe.

We use yarn classic, but there's a newer version of yarn, or things like pnpm, or just npm that are always competing in the package manager space.

Also not this PR for context: #1583. Is there a way for us to support other package managers when the dependency is pulled in directly by projects using other package managers?

Describe the solution you'd like

• An ADR for which package manager this project should use
• An issue or PR updating to use the chosen package manager

Describe alternatives you've considered

• Just stick with what we've got until its a bigger problem (not highly recommended though)
• Use "universally compatible" scripts for build lifecycle to see if that alleviates consumer issues who use different package managers

Additional context

Relates to: #1359

[werdnanoslen]

I want to elevate this, as our outdated yarn version (i.e. pre-Berry/PNP) is now blocking package upgrades (#3491, #2773, #2748, #2734) and requiring at least one workaround to make this upgrade function.

If we go with Yarn PNP (Berry), they have a nice migration guide