introduce changesets to manage release and canary flows

[dotansimha]

No description provided.

[theguild-bot]

The latest changes of this PR are not available as alpha, since there are no linked changesets for this PR.

[ardatan]

@yaacovCR What do you think? We don't need to release all packages for a small change in a one package anymore. We can release them seperately instead thanks to changeset.

[yaacovCR]

Sounds great, you might have to fix a few of my errors as I get used to the new system

[ardatan]

@yaacovCR It's fine!
@dotansimha Is this ready to merge?

[dotansimha]

@yaacovCR it's super simple - as long as your create PRs, and each PR has it's own changeset that declares the release type you need (yarn changeset will guide you). It also handles all changelog and release flows.

@ardatan It's almost ready, this change also means that packages should be able to use other packages using semver ranges, and this is the only missing part. And - we'll need to bump all packages in minor to make sure to propagate the changes related to semver range.

[changeset-bot]

🦋 Changeset detected

Latest commit: 09bc705

The changes in this PR will be included in the next version bump.

Not sure what this means? Click here to learn what changesets are.

Click here if you're a maintainer who wants to add another changeset to this PR

[dotansimha]

@ardatan @yaacovCR
This is ready. Will merge soon.
I adjusted all siblings packages versioning to use ^. This will allow more flexible adjustments.