fix(docs): sort version dropdown branches numerically

[jiwenc-nv]

The docs dropdown inherits Git ref order, so the branch that triggers deployment can appear above main (for example, release/1.6.x).

Sort branches with main first, then releases in ascending numeric order, including 1.9 before 1.10. Tag ordering is unchanged. Two files, no new dependencies.

Validation: make -C docs current-docs; all pre-commit hooks with SKIP=check-copyright-year; template rendering across 120 branch permutations, checking numeric order and selected-version links.

Summary by CodeRabbit

• Documentation
  • Branch options in the version selector are now ordered with main first, followed by branches in numeric and alphabetical order. Tag options remain unchanged. This makes branch versions easier to scan and compare when choosing documentation.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

• Configuration used: Repository: NVIDIA/IsaacCapture/.coderabbit.yaml
• Review profile: CHILL
• Plan: Enterprise
• Run ID: fe937434-4aa4-43ca-ad9a-e6fa22419b6d

📥 Commits

Reviewing files that changed from the base of the PR and between 2fe1bbe and 1f03bb1.

📒 Files selected for processing (2)

• docs/source/_templates/versioning.html
• docs/source/conf.py

Included review availability: This review used your included allowance. Your plan provides up to 12 included reviews per hour; 11 remain after this review.

📝 Walkthrough

The version selector now sorts branch options with sort_doc_branches. The sorter places main first, then sorts branch names by numeric components and lexical order. Sphinx adds the sorter to each page’s template context through the html-page-context event. Tag options remain unchanged.

Priority: ⬇️ Low

Estimated code review effort: 2 (Simple) | ~8 minutes

Merge Risk: ⚪ Minimal · up to 1f03b

The change is limited to ordering documentation branch options; no identified issue warrants delaying merge.

Pre-merge checks · 4 · 1

Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage		Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files. (1 skipped: 1 …	Write docstrings for the functions missing them to satisfy the coverage threshold.

Passed checks (4 passed)

Check name	Status	Explanation
Description Check		Check skipped - CodeRabbit’s high-level summary is enabled.
Title check		The title clearly and concisely describes the main change: numeric sorting of branches in the documentation version dropdown.
Linked Issues check		Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check		Check skipped because no linked issues were found for this pull request.

Full details: Docstring Coverage

Explanation

Docstring coverage is 0.00% which is insufficient. The required threshold is 80.00%. Docstring coverage is scoped to functions touched by this diff. Analyzed 3 functions across 1 files. (1 skipped: 1 unsupported.)

• Fix all pre-merge checks with AI

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

• Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

_{Comment @coderabbitai help to get the list of available commands.}

[github-actions]

📝 Docs preview is not auto-deployed for fork PRs.

A maintainer with write access to NVIDIA/IsaacCapture can deploy a preview by
commenting /preview-docs on this PR. Once deployed, the preview
will live at:

https://nvidia.github.io/IsaacCapture/preview/pr-1256/

[ivany-nv]

Legend: 🚫 BLOCKER = merge-blocking | 💡 SUGGESTION = meaningful improvement | 🧹 NIT = precise small correction

	Finding
🚫	none
💡	none
🧹	none