Reorder and trim the "Past changes" section of PHP Compatibility and WordPress Versions

[johnbillion]

Issue Description

Similarly to #1814 I'm proposing that the "Past changes" section of the PHP Compatibility and WordPress Versions page is reversed chronologically, and some older info is trimmed.

URL of the Page with the Issue

Current page: https://make.wordpress.org/core/handbook/references/php-compatibility-and-wordpress-versions/

Proposed change: https://make.wordpress.org/core/?post_type=handbook&p=117067

Why is this a problem?

We don't need to keep every piece of information around forever. Surplus detail makes it harder for users to quickly find the info they need.

Suggested Fix

https://make.wordpress.org/core/?post_type=handbook&p=117067

@sabernhardt What do you think?

[github-actions]

Heads up @docs-reviewers - the "[Status] Review" label was applied to this issue.

[github-actions]

Heads up @WordPress/docs-issues-coordinators, we have a new issue open. Time to use 'em labels.

[sabernhardt]

Overall, I like these changes. Reverse chronological order is more like a changelog.

Additions that could fit on a separate issue:

1. I think this page could define "beta support" briefly (or link directly to an explanation). In the chronological listing, the introduction of beta support for PHP 8.0 hinted that the dev note might explain it, and the update makes it less of a hint. The term is especially confusing because the first paragraph mentions PHP beta versions, and the "beta" glossary definition does not fit the "beta support" concept.
2. The sentence mentions "Past changes" before indicating the current status. The first chart shows the status, but I would prefer a list earlier like:

The latest WordPress is

• in "beta support" for PHP 8.4 and 8.3
• compatible with documented exceptions (see below) for PHP 8.2, 8.1 and 8.0
• fully compatible with PHP 7.4, 7.3 and 7.2

---

Related Trac ticket

[johnbillion]

Ok I will go ahead and publish those changes, thanks Stephen. Any further tweaks can either be made directly if they're minor or in subsequent issues here.