Update release workflow to retarget latest and v1 tags to the newest v1.x release

[Copilot]

latest and v1 are expected to track the newest stable v1.x release, but both were left pinned to the old v1.5.3 commit while v1.6.1 was already published.
This PR updates release automation so floating tags are advanced on each new v1.*.* release.

• Release tag synchronization

  • Add/update workflow logic to move latest and major tag (v1) to the commit of the newly published v1.*.* tag.
  • Force-update existing tag refs so they do not remain stale after subsequent releases.

• Tag derivation

  • Derive major tag from the release tag (v1.6.1 → v1) to avoid hardcoded major-version behavior.

• Behavioral example

  # On release tag v1.6.1:
  git tag -f v1 <release_commit_sha>
  git tag -f latest <release_commit_sha>
  git push origin refs/tags/v1 --force
  git push origin refs/tags/latest --force