Description

This pull request is to address the problem of no one knows how to update the existing Docker images on the server, except maybe for one person who does not have the time.

Address part of #10483

Removes blocker for #11934

• Why is everything failing? At 2021-08-23 infrastructure tag-up, we have agreed to brute-force update the new truths. Updated at New truths for visualization.wcsaxes astropy-data#116 . I also eyeballed the diffs and nothing shocking, just some labels jittering about.
• Add back disabled job.
• How do we update https://docs.astropy.org/en/latest/development/testguide.html#running-image-tests ?

Checklist for package maintainer(s)

This checklist is meant to remind the package maintainer(s) who will review this pull request of some common things to look for. This list is not exhaustive.

• 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.
• Is a change log needed? If yes, did the change log check pass? If no, add the no-changelog-entry-needed label.
• Is a milestone set? Milestone must be set but astropy-bot check might be missing; 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.