enhance Docker Image Tag release process

[kartikangiras]

Change Description

• When a tag is pushed that follows the v* format (e.g., v1.0.0, v2.1.0), it will push a Docker image tagged with both the specific release version and latest
• Use strict semantic versioning regex (vX.Y.Z) to determine if version
  should be tagged as 'latest'. This future-proofs the pipeline against
  any non-official release suffixes like .rc, .beta, .alpha, etc.

fixes: #9397

Steps to Test

[[ "v1.0.0" =~ ^v[0-9]+\.[0-9]+\.[0-9]+$ ]] && echo "✓ Stable version gets 'latest'" || echo "✗ Failed"
[[ "v1.0.0.rc" =~ ^v[0-9]+\.[0-9]+\.[0-9]+$ ]] && echo "✗ RC should NOT get 'latest'" || echo "✓ RC correctly rejected"
[[ "v1.0.0-beta" =~ ^v[0-9]+\.[0-9]+\.[0-9]+$ ]] && echo "✗ Beta should NOT get 'latest'" || echo "✓ Beta correctly rejected"
python3 -m yaml < .github/workflows/docker.yml && echo "✓ YAML syntax valid"

Pull Request Checklist

Testing

• Your PR passes all CI checks.
• Tests covering the positive and negative (error paths) are included.
• Bug fixes contain tests triggering the bug to prevent regressions.

Code Style and Documentation

• The change is not insubstantial. Typo fixes are not accepted to fight bot spam.
• The change obeys the Code Documentation and Commenting guidelines, and lines wrap at 80.
• Commits follow the Ideal Git Commit Structure.
• Any new logging statements use an appropriate subsystem and logging level.
• Any new lncli commands have appropriate tags in the comments for the rpc in the proto file.
• There is a change description in the release notes, or [skip ci] in the commit message for small changes.

📝 Please see our Contribution Guidelines for further guidance.

[gemini-code-assist]

Note

Gemini is unable to generate a summary for this pull request due to the file types involved not being currently supported.