chore: update Yarn to v4; migrate from Lerna to Yarn Workspaces

[wojtekmaj]

This is an experimental PR to see the potential effect of upgrading Yarn to v4.

Why not Yarn v1:

• It's no longer maintained.
• It has many known bugs.
• It's far slower than virtually every modern competitor (including npm).

Why Yarn v4:

• Fast.
• Very easy, pretty much automatic upgrade.
• Bulit-in workspaces, allowing us to drop Lerna and has all its features built-in.
• Automatic dependency management ("workspace:" protocol) - changes to ^x.x.x where x.x.x is the latest dependency version at the moment of publishing
• Built-in portable shell, allowing us to use e.g. environment variables in scripts, and it'll work on Windows too.

What would make this PR ready for review

• Publishing process - I don't see why it wouldn't work, but I also cannot test it
• Analyzing dependency tree; would running builds in parallel be okay? If so, we can shave off additional 6 seconds from each build.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 0f47404

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

[wojtekmaj]

@diegomura I'd love to know what you think about this!

[diegomura]

I like this!

[wojtekmaj]

I'm glad! Rebased. Working for me.
I don't understand 100% of your workflow though, so I would really appreciate if you could play around with it and see if everything behaves 100% like you expect.

[diegomura]

@wojtekmaj this needs rebase 😄 Sorry, lots of changes going on recently

[wojtekmaj]

lots of changes going on recently

I wonder who can be at fault 🤣 Done.

Just to be sure though, @diegomura did you find some time it works alright and doesn't disrupt your workflow?

I'm more than happy to address any feedback you might have, and this IS a big change!

[wojtekmaj]

Regarding publishing process - my biggest worry was about how version descriptors are managed during publish. Now Yarn handles automatically what Changesets used to do - so we use workspace:^ version descriptors that gets swapped to latest patch version on publish. This seems to be handled well since changesets/changesets#585 so we should be okay!