🎨 improve release notes (ignore minor version)

[matusdrobuliak66]

What do these changes do?

• 🎨 improve release notes (ignore minor version)

Related issue/s

How to test

Dev-ops checklist

• No ENV changes or I properly updated ENV (read the instruction)

[sonarcloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarCloud

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 87.9%. Comparing base (cafbf96) to head (32c0921).
Report is 557 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff            @@
##           master   #6393      +/-   ##
=========================================
+ Coverage    84.5%   87.9%    +3.4%     
=========================================
  Files          10     361     +351     
  Lines         214   18066   +17852     
  Branches       25       0      -25     
=========================================
+ Hits          181   15898   +15717     
- Misses         23    2168    +2145     
+ Partials       10       0      -10     

Flag	Coverage Δ
unittests	87.9% <100.0%> (+3.4%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

Files with missing lines	Coverage Δ
...r/src/simcore_service_webserver/statics/_events.py	92.7% <100.0%> (ø)

... and 370 files with indirect coverage changes

[pcrespov]

This solution is possible but IMO very restrictive. The main idea here should rather be passing as much information to the template_url formatter so that we are as flexible as possible to compose the url
Let me illustrate you with an example, if we instead deduce and pass more granulated information to the formatter like major, minor, etc

#lets assume
template_url = product.vendor["release_notes_url_template"]

data["vcsReleaseUrl"] = template_url.format(vtag=vtag, major=major, minor=minor, patch=patch)

then in the database (which s more convenient) we could redo at any time the url template without. Here some examples

release_notes_url_template = "https://mydoc/{vtag}".  # old template format
release_notes_url_template = "https://mydoc/v{major}.{minor}.0" # new 
# ...
release_notes_url_template = "https://mydoc/v{major}/{minor}.md" # my prediction for 2025's format

So, in summary

1. do not modify vtag but rather inject more information to the formatter. Note that your solution, even if correct, is "removing" information.
2. if _RE_PRODUCTION_RELEASE_VERSION is so relevant, the it MUST be part of the definition of app_settings.SIMCORE_VCS_RELEASE_TAG, i.e. we should not accept non-conformal strings for this input. If you do not want to fail upon validation then create a pre-validator that nullifies with a warning it if it is invalid
   • if the format of this field is guranteed, then it is very easy to extract major, minor and patch from this. e.g. v = packaging.version.Version(app_settings.SIMCORE_VCS_RELEASE_TAG.removeprefix("v")), v.major, v.minor