Rebuild axosyslog image with auto patch version increment

[mitzkia]

After this PR when we request a new stable image job the axosyslog patch version will increment automatically

[mitzkia]

I would like to provide a test job run (from my fork) here (AxoSyslog stable image), but until now it fails every time on image build.

update:
it seems works :) :
https://github.com/mitzkia/axosyslog/actions/runs/12154279030/job/33894119353

[mitzkia]

The PR is ready for the review.
I have the following proof runs:

1. When the actual git tag version is greater than the previous docker tag version

for example:
CI job link (in my fork): https://github.com/mitzkia/axosyslog/actions/runs/12752419559/job/35542271733
actual git tag: 4.99.0
previous docker tag: 4.9.0-2
next docker tag will be: 4.99.0-1

2. When the actual git tag version is equals with the previous docker tag version

for example:
CI job link (in my fork): https://github.com/mitzkia/axosyslog/actions/runs/12753284689/job/35545260970
actual git tag: 4.9.0
previous docker tag: 4.9.0-2
next docker tag will be: 4.9.0-3

3. When the actual git tag version is less than the previous docker tag version in this case the compare script
   will display a warning and will exit

4. Check the generated docker image tags with:

skopeo inspect docker://ghcr.io/mitzkia/axosyslog:latest | jq '.RepoTags'
[
  "dev-main",
  "dev-main-dbg",
  "4.9.0-3",
  "4.9.0",
  "latest",
  "4.9.0-dbg",
  "4.9.0-3-dbg",
  "latest-dbg",
  "4.99.0-1",
  "4.99.0",
  "4.99.0-dbg",
  "4.99.0-1-dbg"
]

[MrAnno]

This must have been really difficult to test properly, thank you for going through everything.

[MrAnno]

Thank you. LGTM.

I think we need to test 3 scenarios and we can merge it:

• axosyslog-nightly.yml should produce a nightly without problems
• 4.99.0 release should produce an image with tags 4.99.0-1, 4.99.0, latest
• triggering a rebuild on 4.9.0 should bump the rebuild version: 4.9.0-3, 4.9.0, latest