Add version selector back to functorch docs

[zou3519]

Stack from ghstack:

• -> Add version selector back to functorch docs #86602

I accidentally deleted it in
#85856 . This brings the version
selector back.

[pytorch-bot]

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/86602

• 📄 Preview Python docs built from this PR
• 📄 Preview C++ docs built from this PR
• ❓ Need help or want to give feedback on the CI? Visit our office hours

Note: Links to docs will display an error until the docs builds have been completed.

✅ No Failures

As of commit 7717d81:
💚 Looks good so far! There are no failures yet. 💚

This comment was automatically generated by Dr. CI and updates every 15 minutes.

[zou3519]

Note to self: this also needs to be cherry-picked to release branch

[zou3519]

Docs preview available at https://docs-preview.pytorch.org/86602/functorchdocs/index.html , note the version selector: (the triangle is clickable)

[samdow]

Wait I might have been premature in my approve haha
Is this what we're trying to fix? I still see this in the docs build from this PR?

No dropdown

Previous version has dropdown

Edit: nvm I was looking at the wrong version. It looks fine on the docs preview build

[zou3519]

Yeah, the previous version of the nightly docs have no dropdown. In the preview for this PR, there is a dropdown.

All the stable docs (0.2.1, etc) are built a single time and never updated so they aren't affected.

[zou3519]

@pytorchbot merge -f "docs-only change; docs CI ran already"

[pytorchmergebot]

Merge started

Your change will be merged immediately since you used the force (-f) flag, bypassing any CI checks (ETA: 1-5 minutes).

Learn more about merging in the wiki.

Questions? Feedback? Please reach out to the PyTorch DevX Team

Advanced Debugging

Check the merge workflow status
here

[github-actions]

Hey @zou3519.
You've committed this PR, but it does not have both a 'release notes: ...' and 'topics: ...' label. Please add one of each to the PR. The 'release notes: ...' label should represent the part of PyTorch that this PR changes (fx, autograd, distributed, etc) and the 'topics: ...' label should represent the kind of PR it is (not user facing, new feature, bug fix, perf improvement, etc). The list of valid labels can be found here for the 'release notes: ...' and here for the 'topics: ...'.
For changes that are 'topic: not user facing' there is no need for a release notes label.