DOC: Fix RTD

[pllim]

Description

Do not use Sphinx 7.2.0 because it is incompatible with pydata-sphinx-theme. Sphinx just released 7.2.1 but not sure why RTD refuses to pick it up on rebuild triggers.

Fix #15193

Blocked by:

• Need new release to be compatible with Sphinx 7.2.x sphinx-automodapi#176

• Wait for new sphinx-gallery release and then remove pin to its dev version (0.14.0 was released 2023-08-18)

Related issues:

• Incompatibility with Sphinx dev pydata/pydata-sphinx-theme#1404
• MAINT: Fix for Sphinx 7.2 sphinx-gallery/sphinx-gallery#1176
• [ANNOUNCEMENT] Potential Breaking Changes in Sphinx 7.2.x sphinx-doc/sphinx#11608

• By checking this box, the PR author has requested that maintainers do NOT use the "Squash and Merge" button. Maintainers should respect this when possible; however, the final decision is at the discretion of the maintainer that merges the PR.

[github-actions]

Thank you for your contribution to Astropy! 🌌 This checklist is meant to remind the package maintainers who will review this pull request of some common things to look for.

• Do the proposed changes actually accomplish desired goals?
• Do the proposed changes follow the Astropy coding guidelines?
• Are tests added/updated as required? If so, do they follow the Astropy testing guidelines?
• Are docs added/updated as required? If so, do they follow the Astropy documentation guidelines?
• Is rebase and/or squash necessary? If so, please provide the author with appropriate instructions. Also see instructions for rebase and squash.
• Did the CI pass? If no, are the failures related? If you need to run daily and weekly cron jobs as part of the PR, please apply the "Extra CI" label. Codestyle issues can be fixed by the bot.
• Is a change log needed? If yes, did the change log check pass? If no, add the "no-changelog-entry-needed" label. If this is a manual backport, use the "skip-changelog-checks" label unless special changelog handling is necessary.
• Is this a big PR that makes a "What's new?" entry worthwhile and if so, is (1) a "what's new" entry included in this PR and (2) the "whatsnew-needed" label applied?
• Is a milestone set? Milestone must be set but we cannot check for it on Actions; do not let the green checkmark fool you.
• At the time of adding the milestone, if the milestone set requires a backport to release branch(es), apply the appropriate "backport-X.Y.x" label(s) before merge.

[github-actions]

👋 Thank you for your draft pull request! Do you know that you can use [ci skip] or [skip ci] in your commit messages to skip running continuous integration tests until you are ready?

[AA-Turner]

@pllim pleae test with Sphinx 7.2.2, which has just been released.

A

[pllim]

Direct backport as 83bc27b