Clarify version behavior in csolution

[ReinhardKeil]

The Problem

The exact behavior of version is not documented with CMSIS-Toolbox. While CMSIS-Toolbox uses in general semantic versioning there are some open questions:

https://open-cmsis-pack.github.io/cmsis-toolbox/YML-Input-Format/#pack-name-conventions shows that version format can be:

major.minor.patch-pre

Q1: What is the impact of using -pre in a version number. Are no pre-release packs accepted without it?

The PDSC documentation allows to use also:

• major.minor which implies patch version 0. Q2: Is this also the behavior in CMSIS-Toolbox?
• 25.01 or 25.02.17 to allow calendar versioning (https://calver.org/). Q3: can a version be prepended with 0?

PDSC versions can be used at component, pack, config files.

Q4: is the version format identical on all this?
Q5: -pre for config files. Is this supported?

Q6: Is for components the format @^version and @~version supported?

Relates to #1936