docs: clean README main-branch references for r26.07

[mc-nv]

What does the PR do?

Converts the 9 remaining GitHub documentation links in the top-level README.md from the main branch to the r26.07 release branch, so that the release-branch README points readers at release-branch docs.

Links updated (/blob/main/ → /blob/r26.07/, /tree/main/ → /tree/r26.07/):

• backend/docs/python_based_backends.md
• backend/docs/backend_platform_support_matrix.md
• backend/README.md
• perf_analyzer/README.md
• client/src/c++/examples, src/python/examples, src/java/.../examples
• server/docs/protocol/extension_binary_data.md
• python_backend/inferentia

All target paths were verified to exist on each repo's r26.07 branch. The Java source path segment src/main/java/... is intentionally left unchanged (it is a source directory, not a branch ref).

Checklist

• PR title follows Conventional Commits
• Only README.md changed
• Links verified against r26.07 branches

Related

Linear: TRI-1594 — [Before NGC Release] Update release docs

[greptile-apps]

Greptile Summary

This PR updates 9 GitHub documentation links in the top-level README.md, replacing main-branch refs with r26.07 release-branch refs, so the release-branch README consistently points readers at release-branch docs.

• /blob/main/ and /tree/main/ URL segments are replaced with /blob/r26.07/ and /tree/r26.07/ across links to the backend, perf_analyzer, client, server, and python_backend repositories.
• The src/main/java/… path segment in the Java client examples URL is correctly left unchanged, as it is a source directory path, not a branch reference.
• A trailing newline is inadvertently removed from the final line of the file.

Confidence Score: 4/5

Safe to merge — only documentation links are changed, and all nine link updates correctly swap the main branch ref for r26.07.

All link replacements look correct and the Java source-directory path is intentionally preserved. The only unintended change is the removal of the trailing newline on the last line of the file.

No files require special attention beyond the missing trailing newline at the end of README.md.

Important Files Changed

Filename	Overview
README.md	9 GitHub links correctly updated from /blob/main/ or /tree/main/ to /blob/r26.07/ or /tree/r26.07/; trailing newline inadvertently removed from the last line.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[README.md on r26.07 branch] --> B{Link type}
    B -->|/blob/main/ → /blob/r26.07/| C[backend/docs/python_based_backends.md]
    B -->|/blob/main/ → /blob/r26.07/| D[backend/docs/backend_platform_support_matrix.md]
    B -->|/blob/main/ → /blob/r26.07/| E[perf_analyzer/README.md]
    B -->|/blob/main/ → /blob/r26.07/| F[client: C++ examples]
    B -->|/blob/main/ → /blob/r26.07/| G[client: Python examples]
    B -->|/blob/main/ → /blob/r26.07/| H[client: Java examples]
    B -->|/blob/main/ → /blob/r26.07/| I[server/docs/protocol/extension_binary_data.md]
    B -->|/blob/main/ → /blob/r26.07/| J[backend/README.md]
    B -->|/tree/main/ → /tree/r26.07/| K[python_backend/inferentia]
    B -->|unchanged - source dir, not branch| L[src/main/java/... path]

Loading

_{Reviews (1): Last reviewed commit: "docs: clean README main-branch reference..." | Re-trigger Greptile}

[greptile-apps]

The final line is missing a trailing newline. This was present in the base branch (-for more information. had a line ending) but was dropped in this commit, as indicated by the \ No newline at end of file marker in the diff. Many tools and linters treat a missing trailing newline as malformed.

Suggested change

	for more information.
	for more information.

[mc-nv]

Closing as duplicate of #8904 (identical README cleanup for TRI-1594). Consolidating on #8904 from branch mchornyi/TRI-1594/before-ngc-release-update-release-docs.