build: rewrite release script in Python

[nyg]

Summary

Replaces scripts/create-release.sh, which hard-coded the release and development versions, with scripts/create-release.py, run as scripts/create-release.py patch|minor|major.

The script:

• aborts if examples/src/main/resources/api-keys.properties exists, so a real key file cannot end up in a release build;
• fetches tags from origin and takes the highest v* tag as the current version, so a stale clone cannot compute an already released version, and bumps it: patch 4.0.0 → 4.0.1, minor → 4.1.0, major → 5.0.0, with the next development version set to the release's patch + 1 as -SNAPSHOT;
• asks for confirmation, then runs mvnd --serial -Dtag=vX -DreleaseVersion=X -DdevelopmentVersion=… release:prepare release:perform from the repository root;
• offers to open https://central.sonatype.com/publishing, where the validated deployment is published manually.

docs/RELEASE.md now describes the script in its Summary section.

Design notes

• The current version comes from the latest tag, not from the POM: the POM already holds X.Y.(Z+1)-SNAPSHOT after a release, so bumping the patch from it would skip a version.
• The script calls mvnd, matching the --serial flag used in docs/RELEASE.md.
• It only uses the Python standard library.

Testing

Ran the script with no argument, an invalid argument, and each of patch, minor and major, declining the confirmation prompt; the computed versions were 4.0.1, 4.1.0 and 5.0.0 respectively. With a dummy api-keys.properties in place, it aborted before computing versions. The actual Maven release and browser prompt have not been exercised.

[sonarqubecloud]

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 SonarQube Cloud