Ruff fix isort - #14843

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 "When to rebase and squash commits".
• 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.

👋 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?

Do we at least want to backport to v5.3.x to lower risk of backport conflicts?

Once the milestone is sorted out (pun?), we can merge.

Do we at least want to backport to v5.3.x to lower risk of backport conflicts?

Agreed!

@meeseeksdev backport to v5.3.x

Argh, I guess not. @nstarman , are you interested in a manual backport? If not, we can move the milestone back. Thanks!

I'll give it a look.

We could do it, but only if we backport the .ruff.toml file.

👀 Well, if you find out that fixing .ruff.toml isn't easy in v5.3.x branch, then we don't have to. Though... we just cut v5.3.x not that long ago. Has it diverged from main that much already?!

We split .ruff.toml out from pyproject.toml, so it's really only diverged at that point.

@nstarman , I am just going to change the milestone, since v5.3 is already released. Thanks!