[core] Version bump script improvements

[DiegoAndai]

An issue to collect improvements we need for the version bump script (release:version)

• When bumping to a new major or prerelease tag (e.g.,alpha to beta) the script should bump all packages regardless of whether they have changes or not.
  • Discovered in [release] 7.0.0-beta.2 #45435
• When a package which follows Material UI versions (e.g., @mui/material, @mui/utils, @mui/system) was skipped in a previous release (because it had no changes) and has to be bumped in the next release (because now it has changes), the script should propose the root's package.json version for it
  • For example, if @mui/utils last release was 1.0.0 and the next Material UI version is 1.0.2, the script should propose 1.0.2 instead of 1.0.1.
  • Discovered in [release] v7.0.0-beta.3 #45484 (comment)

[DiegoAndai]

@Janpot I've created this issue to collect improvements we've discussed about the version bump script. I'll leave it up to you and the @mui/code-infra team to prioritize it.

[Janpot]

When a package which follows Material UI versions (e.g., @mui/material, @mui/utils, @mui/system) was skipped in a previous release (because it had no changes) and has to be bumped in the next release (because now it has changes), the script should propose the root's package.json version for it

But we explicitly want independent versioning. Why does it only have to catch up with latest version once there is a change. i.e. In your example: why is it ok for @mui/[email protected] to depend on @mui/[email protected] but it's not ok for @mui/[email protected] to depend on @mui/[email protected]? We either do independent versioning or we don't, I don't really see the benefit of creating a hybrid.