Don't update legacy containers

[johnbillion]

Fixes #175.

To test

1. Make an update to a legacy container config in update.php
2. Run php update.php
3. Confirm the corresponding images/x.y files were not updated

[github-actions]

The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the props-bot label.

If you're merging code through a pull request on GitHub, copy and paste the following into the bottom of the merge commit message.

Co-authored-by: johnbillion <[email protected]>
Co-authored-by: desrosj <[email protected]>

To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook.

[desrosj]

There were 3 commits making changes to these legacy containers since they were removed from the build workflows that I've reverted here.

It's highly unlikely that these will ever be rebuilt again. But just in case, I think it makes sense to return these images back to the state of their last successful build and publishing.

[desrosj]

@johnbillion There are a few other open PRs that would update legacy containers without this PR being merged first.

I wanted to make sure that you agreed with removing the changes to the Dockerfiles for these older versions that remain unpublished before merging.