Implement Semantic Versioning and Automated Version Updates for Release Builds

[Freezor]

Description

This pull request introduces changes to the release build script to adopt semantic versioning. The version format now follows the pattern: coreversion-buildnumber-aasmodel-suffix-buildsuffix. e.g.: 0.3.0-2-aasV3-alpha-develop

!This PR is based on the changes of this PR: https://github.com/eclipse-aaspe/server/pull/259

Changes Summary:

1. Semantic Versioning Implementation:

   • Core Version: The base version of the project.
   • Build Number: A constantly incremented value after each build.
   • AAS Model: Currently hardcoded to aasV3.
   • Suffix: Currently hardcoded to alpha.
   • Build Suffix: Determined by the branch from which the release is initiated (latest for main, stable for release, and develop for other branches).

2. Automated Version Update in csproj Files:

   • The script now updates the <Version> tag in all .csproj files in the solution with the generated semantic version.

Motivation and Context

This change is required to standardize the versioning system, making it easier to track and manage releases. Semantic versioning provides clear and structured version information, aiding in better release management and integration processes.

Type of change

• [x] New feature (non-breaking change which adds functionality)
• [x] This change requires a documentation update

How Has This Been Tested?

• The changes were tested by running the updated release build script and verifying that the generated version follows the specified format.
• Ensured that the <Version> tags in all .csproj files are correctly updated with the generated version.

Screenshots (if appropriate):

Checklist:

• [x] My code follows the style guidelines of this project
• [x] I have commented my code, particularly in hard-to-understand areas
• [x] I have made corresponding changes to the documentation
• [x] I have added tests that prove my fix is effective or that my feature works

---