Use annotated tags when releasing

[dduportal]

In jenkins-infra/helpdesk#3084 (comment), we ran into an issue where Jenkins was not triggering builds for a given tag because the timestamp was not when the release was published but when the release-drafter tag was initially created.

This is caused by the fact the punlishing a GitHub release generates a ligthweight git tag as per https://github.com/orgs/community/discussions/4924 .

The tag is created by

jenkins-maven-cd-action/run.sh

Line 12 in 8c5d1f5

gh api -X PATCH -F draft=false -F name=$version -F tag_name=$version /repos/$GITHUB_REPOSITORY/releases/$release

which publishes the GH release created by release-drafter (through the GH api).

We were able to fix the issue on our custom made library by adding the -a flag when creating our tag in the Jenkins infra (ref. jenkins-infra/pipeline-library#360) , but it is a "pure git" solution.

Not sure how to solve this issue there, maybe updating the tag created by the published release to annotate it?