post: Update default branch post-26.05

[mc-nv]

^{CI (internal): #52829374}

What does the PR do?

Cherry-pick of r26.05#191 ("fix: streamline library distribution for 26.05 upstream container build") to main: removes an absent reference and changes library distribution out of the PyTorch image. Required so main can build against the 26.05 upstream container.

Changed files: CMakeLists.txt.

Checklist

• I have made sure this PR is not a duplicate.
• I have made sure the commit message is clear and follows Conventional Commits.
• I have added unit tests for any new functionality.
• I have made sure all tests are passing.
• For documentation changes: I have previewed the changes and they render correctly.

Commit Type:

• feat (A new feature)
• fix (A bug fix)
• docs (Documentation-only changes)
• style (Changes that do not affect the meaning of the code — formatting, whitespace, etc.)
• refactor (A code change that neither fixes a bug nor adds a feature)
• perf (A code change that improves performance)
• test (Adding missing tests or correcting existing tests)
• build (Changes that affect the build system or external dependencies)
• ci (Changes to CI configuration files and scripts)
• chore (Other changes that don't modify src or test files)

Related PRs:

• post: Update default branch post-26.05 server#8804
• post: Update default branch post-26.05 model_analyzer#1024
• post: Update default branch post-26.05 tensorrtllm_backend#857

Original (r26.05): #191

Where should the reviewer start?

CMakeLists.txt

Test plan:

Cherry-pick of an already-merged fix on r26.05; verified against the 26.05 upstream container build.

• CI Pipeline ID: 52829374

Caveats:

Cherry-pick from r26.05.

Background

Part of TRI-1063 post-26.04 release maintenance: forward-port the 26.05 library-distribution fix so main builds cleanly against the 26.05 upstream container.

Related Issues:

Resolves: TRI-1063

[whoisj]

What's happening here?

[mc-nv]

There was a change on PyTorch side.
We review the changes inside the container and libraries dependency to address names which are used by PyTorch.
For now this condition satisfies the build scenario, next release may or may not require respective change.