chore(version): Update development version 2.70.0 / 26.06

[mc-nv]

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

What does the PR do?

After 26.05 code freeze, main now tracks 26.06 development. Bumps TRITON_VERSION and build.py version map.

• TRITON_VERSION: 2.69.0dev → 2.70.0dev
• build.py release_version: 2.69.0dev → 2.70.0dev
• build.py triton_container_version: 26.05dev → 26.06dev

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

Related PRs:

• chore(version): Update development version 1.55.0 / 26.06 model_analyzer#1022
• dl/dgx/tritonserver!1765
• dl/dgx/tritonmodelanalyzer!177

Where should the reviewer start?

• TRITON_VERSION
• build.py DEFAULT_TRITON_VERSION_MAP

Test plan:

Verified locally that version values match the next-release tracking expected after 26.05 code freeze.

• CI Pipeline ID: 51176860

Caveats:

None.

Background

Standard post-code-freeze housekeeping per the Triton Release runbook.

Related Issues:

• Resolves: TRI-1047