CI: Add a set of scenarios to test RC and Final tagged release behavior #3054
Description
As for the build breakage per se - I was surprised too; CI builds (of not-tagged code) went along with that PR's change just fine.
Originally posted by @jimklimov in #3053
A new bump in the matrix: git tag -asm '...' locally on various platforms and make sure build still succeeds.
Check that for builds from make dist archives, their self-identification exposes the expected release (or pre-release of N as iteration after N-1).
MAYBE limit this to specially-named branches, to minimize time costs in usual CI iterations.
It is very unpleasant to wake up hoping that the release is today, and spend that day fighting edge cases that only pop up on tagged code and only some build agents.