Fetch besu version from CHANGELOG.md instead of latest release tag on main #4210

Hi Besu team, we're having a release versioning issue from Besu when making a linea-besu release (which builds at a commit hash from besu-eth/besu and set the release version as "the last tag reachable from the commit" plus the "commit hash", e.g.  26.8.1-d97cbd6 ), however the issue comes sometimes when we try to make a linea-besu release with a more recent commit on main, e.g. efa817c, and in this case, the release version would become 26.7.0-efa817c, which by telling the semantic version, our external partners or even automatic software deployment tools might get confused and assumes it was a version downgrade, even though it indeed contains all the changes from 26.8.1 plus some other more recent commits. (as the case here)

So our question is how could we do to avoid that in the future? how does your team decide when to release on main (like 26.7.0) and when on branch (like 26.8.1 )? Is there any concerns on always releasing on main ? or is it possible to make a release tag with suffix to indicate a candidate release (e.g. 26.8.1-rc1) for branch releases, and then tag probably as 26.8.1 on main when merging back the release branch to main? any feedback is welcome, thx!