Switching to fixed versioning for Spark packages

[Powerplex]

We had many issues related to our consumers updating one package and not another. Sometimes it is causing two versions of a library to be installed.

Example:

@spark-ui/dialog@latest is using @radix-ui/dialog@1.1.0
@spark-ui/drawer@latest is also using @radix-ui/dialog@1.1.0

But on a consumer website, an earlier version than latest is installed just for Dialog, this earlier version is using @radix-ui/dialog@1.0.0

The page now loads two versions of the same library, and it causes some critical bugs.

We suggest to switch Spark from independant versioning to fixed versionning, like many other libraries or design system, like Storybook here for example:

"@storybook/addon-a11y": "^8.0.2",
"@storybook/addon-actions": "^8.0.2",
"@storybook/addon-essentials": "^8.0.2",
"@storybook/addon-interactions": "^8.0.2",
"@storybook/addon-links": "^8.0.2",

=> all packages shares a same version.

Let's weight the pros and cons and the strategy to implement this.

[Powerplex]

We decided to preserve the package naming. It means that we must start the version number from 5.0.0.

this is because the package with the highest version is @spark-ui/theme-utils: 4.1.1.

We will republish every package in 5.0.0, after setting up Lerna to publish in fixed versioning: https://lerna.js.org/docs/features/version-and-publish#fixedlocked-mode-default

We must set the force-publish flag to allow Lerna to publish every package in a synchronized way.

[Powerplex]

The PR: #2309