post: Advance main to 26.05dev

[mc-nv]

^{CI (internal): #49752351}

What does the PR do?

Updates development version strings in __init__.py files to reflect the post-26.04 / 26.05dev cycle.

Changed files include: genai-perf/genai_perf/__init__.py, src/perf_analyzer/__init__.py.

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: Advance main to 26.05dev server#8760
• post: Advance main to 26.05dev client#893
• post: Advance main to 26.05dev model_analyzer#1021
• post: Advance main to 26.05dev onnxruntime_backend#341

Where should the reviewer start?

genai-perf/genai_perf/__init__.py, src/perf_analyzer/__init__.py

Test plan:

Release-maintenance change; no new behaviour introduced.

• CI Pipeline ID: 49752351

Caveats:

None.

Background

Part of TRI-912 post-26.04 release maintenance: advance all Triton main/master branches to 26.05 / 2.69.0dev before the NGC 26.04 container is published.

Related Issues:

Resolves: TRI-912