chore: Update main to track development for 2.71.0dev / r26.07

[mc-nv]

What does the PR do?

Advance main to track the next development train. Bumps TRITON_VERSION and DEFAULT_TRITON_VERSION_MAP.triton_container_version in build.py so post-code-freeze main work targets 2.71.0dev / 26.07dev.

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.
• All template sections are filled out.

Commit Type:

• chore (via chore: prefix; conventional commits)

Related PRs:

triton-inference-server/model_analyzer#1025

Where should the reviewer start?

• TRITON_VERSION — string bump.
• build.py (DEFAULT_TRITON_VERSION_MAP) — release_version and triton_container_version keys.

Test plan:

Pure version-string change; CI sanity verifies the new map is read correctly.

• CI Pipeline ID: 54495118

Caveats:

• upstream_container_version (26.05) and ort_* versions are intentionally left untouched — those move on a separate cadence.

Background

Standard "At Code Freeze" step for the 26.06 release train: snap main forward so day-after work targets the next train.

Related Issues:

• Resolves: TRI-1415