chore(post-release): Update default branches post-26.07

[mc-nv]

What does the PR do?

Carries the two r26.07 commits main genuinely lacks into main as part of the
post-26.07 default-branch advance:

• chore(versions): align tutorials examples with 26.07 release train (chore(versions): align tutorials examples with 26.07 release train #155) — moves the
  example container tags from the 26.06 train to 26.07 across 19 files.
• build(dependencies): Bump dependency version (build(dependencies): Bump dependency version #161).

7b46cda from r26.07 is deliberately excluded — it is a re-pick of #159 / #162, whose
originals are already on main as 71ad788 and e848952.

Checklist

• PR title reflects the change and is of format <commit_type>: <Title>
• Changes are described in the pull request.
• Related issues are referenced.
• Populated github labels field
• Added test plan and verified test passes.
• Verified that the PR passes existing CI.
• Verified copyright is correct on all changed files.
• Added succinct git squash message before merging ref.
• All template sections are filled out.
• Optional: Additional screenshots for behavior/output changes with before/after.

Commit Type:

Check the conventional commit type
box here and add the label to the github PR.

• build
• ci
• docs
• feat
• fix
• perf
• refactor
• revert
• style
• test

Related PRs:

• chore(post-release): Update default branches post-26.07 server#8909
• build(dependencies): update Tomca version (#912) client#913

Where should the reviewer start?

Popular_Models_Guide/ and Quick_Deploy/ — confirm the container tags read 26.07.

Test plan:

git grep "26\.0[0-6]-" returns no hits in the files touched by this PR.

• CI Pipeline ID: 60058404

Caveats:

Build_Guide/RHEL_Manylinux/README.md still targets 2.69.0 / NGC 26.05. It is main-only
(added by #157 after the r26.07 cut) so the alignment commit never covered it, and its
26.05 references are coupled to a stated CUDA 13.2.1 / TensorRT 10.16.1.11 / PyTorch 2.13.0
tuple — bumping the NGC number alone would make that tuple wrong. Left for a separate doc
refresh.

HuggingFace/README.md and Quick_Deploy/OpenVINO/README.md pin 26.05 upstream images
on both main and r26.07 — pre-existing drift, out of scope here.

Background

Release step "[Before NGC Release] Advance master branch to next upstream release".
Precedent: 69217d9 did the same alignment pick for the 26.06 cycle.

Related Issues: (use one of the action keywords Closes / Fixes / Resolves / Relates to)

• Relates to: TRI-1601

^{CI (internal): [#60058404](http://tritonserver.local/ci/pipelines/60058404)}

[greptile-apps]

Greptile Summary

Advances the tutorials to the 26.07 release train.

• Updates Triton server, SDK, vLLM, and TensorRT-LLM container references from 26.06 to 26.07.
• Updates Python API examples from Ray 2.55.1 to 2.56.1.
• Refreshes copyright headers in affected tutorials and Kubernetes manifests.

Confidence Score: 5/5

The PR appears safe to merge.

No blocking failure remains.

Important Files Changed

Filename	Overview
Triton_Inference_Server_Python_API/build.sh	Aligns default base-image and generated image tags with the 26.07 release.
Triton_Inference_Server_Python_API/deps/requirements.txt	Updates the Ray dependency from 2.55.1 to 2.56.1.
Triton_Inference_Server_Python_API/examples/kafka-io/requirements.txt	Keeps the Kafka example's Ray and Ray Serve dependencies aligned at 2.56.1.
Deployment/Kubernetes/EKS_Multinode_Triton_TRTLLM/multinode_helm_chart/containers/triton_trt_llm.containerfile	Advances the TensorRT-LLM base container to the 26.07 image.
Quick_Deploy/HuggingFaceTransformers/Dockerfile	Advances the quick-deploy base image to Triton Server 26.07.

_{Reviews (3): Last reviewed commit: "chore: update copyright years on cherry-..." | Re-trigger Greptile}