Clarify versioning strategy and document version usage

[noraeb]

Is your feature request related to a problem? Please describe. As a contributor to OpenSCD, I find it unclear how version numbers are managed. There are multiple version numbers across the repository and they don't align. This can cause confusion when trying to understand which version is deployed or shown in the UI.

Describe the solution you'd like I would like a clear and documented versioning strategy that explains:

• Which version number represents the official release.
• How version numbers are updated and used across the repo.
• The version in manifest.json should match the release version.

Requirements

• Documentation of the versioning strategy (e.g., in README.md or CONTRIBUTING.md).
• Automation to sync relevant version numbers during releases. These are: the version in the root package.json and the version in manifest.json

Suggestions for a specific user interaction No

Additional information List of version numbers in this repo:

/package.json: 0.38.1 /packages/openscd/package.json: 0.34.0 /packages/distribution/package.json: 0.0.1 /packages/xml/package.json: 0.0.1 /packages/core/package.json: 0.1.4 /packages/addons/package.json: 0.34.0 /packages/plugins/package.json: 0.0.1 /packages/wizards/package.json: 0.0.1 /packages/distribution/manifest.json: 0.36.0

Test Files n/a

[Sander3003]

Did you bring this already in for refinement?

[Sander3003]

It's ready to go.