Test Details Overview

Rewrite the tag generator

generate_next_git_tag.sh grew its options, globals and output modes
over several rounds and was hard to reason about: it matched tags with
an unescaped dot, force-moved tags and force-pushed the release branch,
and wrote its results to GITHUB_ENV for the workflow to copy into
outputs. ci/deploy/next-tag.sh keeps the scheme (DB tags on develop,
RC tags on the release branch, plain release tags on request, versions
committed into CMakeLists.txt and the release commit pushed to its
branch) in a third of the lines, with a --dry-run that prints the tag
it would create. Pushes are no longer forced, so a collision fails
instead of moving a published tag, and the outputs go straight to
GITHUB_OUTPUT.

The workflow checks out the full history for it: deciding whether the
latest tag already covers HEAD needs the commits between them.

__________

Type: commit

Hash: cf6724dcf203641c490daf3417b5883e2dadc598

Created: yesterday

__________

gr0v1ty/nano-node:cf6724dcf203641c490daf3417b5883e2dadc598