Fix: Skip new ser-ver-id for --release option (custom-release)

[t2gran]

Summary

This PR improve thecustom_release.py with enhanced logic on setting the correct serialization.version.id. The new logic work as follows:

The script will resolve what the next serialization version id (SID) should be. This is a complex task.
Here is an overview:

1. If the --serVerId option exist, then the latest SID is bumped and used.
2. If the --release option exist, then the current pom.xml SID is validated, if ok it is used,
   if not the script exit.
3. All merged in PRs are checked. If a PR is labeled with 'bump serialization id' and the the
   HEAD commit is not in the latest release, then the last release SID is bumped and used.
4. Finally, the script look at the upstream SID for the last release and the base. If the SID
   is not the same the SID of the last release is bumped. To find the upstream SIDs the script
   look at the git history/log NOT matching the project serialization version id prefix - this
   is assumed to be the latest SID for the upstream project.

Tip! If the '--release' option is used, then the serialization version id is NOT updated. Use the
'--serVerId' option together with the '--release' to force update the serialization version id.

The terms "current release" and "new release" was slightly misleading. I changed them to:

• latest release (was current release). The last tagged release.
• next release (was new release) . The new release to be created next. Current is still used to refer to the current content of e.g. pom.xml - next refer to the what the value will be after the release is made.

In addition to these terms the base release is used to refer to the release used as the starting point for the next release - witch might be the latest release, but could be any commit.

Issue

🟥 There is no issue for this.

Unit tests

🟥 There are no tests on the custom release script.

Documentation

✅ The doc is updated.

Changelog

🟥 This is to technical and minor to end up in the release notes.

Bumping the serialization version id

🟥 Does not have any effect on OTP at all.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 71.58%. Comparing base (bb7eba1) to head (83c7234).
Report is 195 commits behind head on dev-2.x.

Additional details and impacted files

@@              Coverage Diff              @@
##             dev-2.x    #6683      +/-   ##
=============================================
+ Coverage      71.40%   71.58%   +0.17%     
- Complexity     18569    18932     +363     
=============================================
  Files           2035     2059      +24     
  Lines          76553    77467     +914     
  Branches        7824     7900      +76     
=============================================
+ Hits           54664    55454     +790     
- Misses         19116    19198      +82     
- Partials        2773     2815      +42     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.