Implement fixed versioning for the react/web-component packages in stable and canary

Nobody has claimed this yet.

## Summary
Implement fixed versioning for the react/web-component packages in stable and canary.

## 💬 Description
Currently, lerna uses "independent" mode which means that the react and web/component packages (and those in canary) can get out of sync, as we want some packages to be "fixed" and the rest "independent".

As far as I can see, there is no functionality to have a mix of fixed and independent versioning in lerna.

A workaround could be to run a script during both the release-check command and the publishing pipeline, that gets the current package versions, determines the highest and updates them all to have the same version (depending on if this works in the process). This solution has not been tested, so some exploration may be needed, as the versions might only change after it has been published, in which case this will not work.

## Why do we need it?
To make the release run smooth, and ensure that it never fails due to the packages not being in sync with each other. Currently we have to add a "feat" commit to the package that needs a bump, which works, but causes delays in the release and means the release notes are not accurate.

Start by tracing the release-check command and publishing pipeline for the stable and canary packages, and inspect how Lerna currently applies independent versioning. Determine how the React and web-component package versions can remain fixed without disrupting the other independent packages; done means releases complete smoothly with those package versions in sync and accurate release notes.

Written by the indexing model from the issue text.