[release-26.3] store os release name and use it than recalculating from tag which is errorprone

[github-actions]

🤖 Automated backport of #2244 to release-26.3

⚠️ This PR has merge conflicts that need manual resolution.

Original PR: #2244
Original Author: @rahulait

Cherry-picked commits (1):

• 6afb205 store os release name and use it than recalculating from tag which is errorprone

Next Steps:

1. Review the conflicts in the "Files changed" tab
2. Check out this branch locally: git fetch origin backport-2244-to-release-26.3 && git checkout backport-2244-to-release-26.3
3. Resolve conflicts manually
4. Push the resolution: git push --force-with-lease origin backport-2244-to-release-26.3

---

Instructions for resolving conflicts

git fetch origin backport-2244-to-release-26.3
git checkout backport-2244-to-release-26.3
# Resolve conflicts in your editor
git add .
git commit
git push --force-with-lease origin backport-2244-to-release-26.3

[copy-pr-bot]

This pull request requires additional validation before any workflows can run on NVIDIA's runners.

Pull request vetters can view their responsibilities here.

Contributors can view more details about this message here.

[rahulait]

/ok to test d277642

[rahulait]

/ok to test 01ad7d1

[coveralls]

coverage: 27.951% (+0.2%) from 27.79% — backport-2244-to-release-26.3 into release-26.3

[tariq1890]

@rahulait Has this PR been rebased on top of #2267 ?

[rahulait]

@rahulait Has this PR been rebased on top of #2267 ?

Yeah, it is. Current backport branch is 1 commit ahead of release-26.3 branch

git rev-list --left-right --count release-26.3..backport-2244-to-release-26.3
0	1

Initially it contained changes of #2267 in this PR as well (see commit 9652102). I had to get the #2267 merged first into release-26.3 so that I can have this PR independent of the changes of other PR.