[no-relnote] Backport release tooling changes

[elezar]

These changes backport the release tooling changes needed to release images using the updated process.

The changes on main were done in:

• Integrate ngc automation #1181
• [no-relnote] Fix type in publish script #1187
• [no-relnote] Fix type in publish script #1188
• [no-relnote] Override publishing path #1211
• [no-relnote] Don't let scan failures block pipeline #1212

[ArangoGutierrez]

My only question on this PR is why the original Commits are not cherry-picked and then, IF needed, an extra commit to fix any merge conflicts.

[elezar]

My only question on this PR is why the original Commits are not cherry-picked and then, IF needed, an extra commit to fix any merge conflicts.

The short answer: Because tracking down the commits and then making sure that everything lines up with the expectations on this branch seemed like a lot of effort for a quick fix to align the release process on the maintenance branch.

Update: The differences in the .nvidia-ci.yml file between the parent of the first commit and what is present on the release-1.17 branch at the moment are already such that a clean cherry-pick is not possible.