feat: consistent git tag behavior across all publishing workflows

[tehw0lf]

Summary

Standardizes git tag handling across all publishing workflows to a consistent pattern:

• Git tag: set explicitly if not yet present, ::warning:: if already exists (never fail)
• GitHub Release (where applicable): ::warning:: + skip if release already exists (previously exit 3)

Changes per workflow

Workflow	Before	After
release-github.yml	exit 3 if release exists	Explicit git tag step (warn+skip if exists) + warn+skip if release exists
release-android-apk.yml	exit 3 if release exists	Same as above
publish-npm-libraries.yml	No git tag at all	Git tag from package.json, warn+skip if exists
publish-python-libraries.yml	::notice:: if tag exists	::warning:: for consistency
publish-docker-image.yml	No git tag at all	Git tag from version extraction, first matrix job only, warn+skip if exists

Notes

• Docker git tag only runs on matrix.docker == fromJson(inputs.docker_meta)[0] since the tag is independent of platform
• softprops/action-gh-release handles pre-existing tags gracefully (reuses them), so the explicit tag step is safe
• Race conditions between parallel workflows (e.g. npm + github release) are handled: both try to set the tag, one succeeds, the other warns and continues

Test plan

• Trigger a workflow run where the tag does not exist yet → tag should be created
• Re-trigger the same version → warning logged, release step skipped, workflow succeeds