Publish scripts only update changed packages

[tsmaeder]

Bug Description:

While doing a patch release following the instructions, I ended only publishing the packages which had changes since the last publish. This seems consistent with the lerna doc, since we're not passing --force-publish to lerna in the package scripts.

Steps to Reproduce:

1. Follow the publishing instruction, I used npm run publish:latest to publish theia
2. Observe: you end up with only a couple of published packages
3. Observe: lerna reports it published 76 packages, which is not true 🤷

Additional Information

• Operating System: Ubuntu 22.04
• Theia Version: 1.58.x

[tsmaeder]

I propose that instead of doing an immediate lerna publish we do a lerna version first. We can then compare the outcome to our expectations and then either lerna publish --fromPackage (or whatever the right flag is) or reset the changes via git and try again.
In the long run, publishing should be done via a github workflow, IMO.

[sgraband]

Another idea would be to do something similar to what the Theia IDE does: script.

[tsmaeder]

Additional info: I don't think a missing --force-publish parameter is the issue: we configure this in lerna.json and when I observe the lerna publish run, it first creates ~80 changes (as seen with git status and after the publish, some of these changes seem to be reverted. Is it my machine? Is this a spurious problem? Needs to be investigated.