[Feature]: migrate v9 packages to new unstable release versioning

[Hotell]

Library

React Components / v9 (@fluentui/react-components)

Describe the feature that you would like added

Right now we use pre-release versions starting 9.0.0-alpha.0 for v9 packages creation flow which is exposed to public via our suite package (@fluentui/react-components ) via /unstable import path.

After receiving feedback from consumers we will change this approach to properly follow semver in all phases of our development/release cycle.

What's gonna change:

• we will no longer use prerelease versioning nor add/expose those apis via /unstable path from react-components suite
• all new v9 packages will embrace following approach
  • 0.x.x versioning scheme
  • -preview suffix within name ( eg: @fluentui/react-lightstaber-preview@0.x.x )
• all existing v9 packages that are already released as unstable with pre-release version will embrace following approach:
  • TBA
• going from unstable(preview) to stable
  • existing preview package will be renamed by removing the -preview suffix ( eg: @fluentui/react-lightstaber-preview -> @fluentui/react-lightstaber
  • package will be released as stable 9.0.0 and it will be available from within react-components suite

Have you discussed this feature with our team

Leadership/Core team

Additional context

https://github.com/microsoft/fluentui/wiki/new-release-process---v9-packages

Validations

• Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

Remaining Task

• document new process
• implement automation for initial releases preparation (preview,stable)
• npm deprecate preview package when its being released as stable on CI
  • [Internal] Deprecate -preview packages already published as stable #30541