Test confirming appropriate MariaDB requirements is currently failing

[desrosj]

As of June 17, 2025, the test_readme_mariadb_version() test method is failing.

It appears that MariaDB has redesigned their documentation. The ​previous URL now redirects to ​a new one. Confirmed the old design in the ​Way Back Machine.

This change aside, this test would have started failing anyway on ​24 June 2025 when the 10.5 release reaches end-of-life.

[desrosj]

In 60313:

Database: Temporarily skip the test_readme_mariadb_version test method.

The layout and structure of the release documentation pages for MariaDB have been changed. The related test is now unable to parse the date from the first release of a given version.

Long-term releases from MariaDB are supported for a total of 5 years before reaching end of life. That milestone will be reached next week, so this test would have started to fail then anyway.

This marks the test as skipped temporarily so that the test’s methodology can be improved to account for all of this.

Props jorbin, johnbillion.
See #63586.

Updates the MariaDB test to pull the data from the WikiData API rather than attempting to parse the HTML on the MariaDB home page.

Pulls in the software version from the datasource at ​https://www.wikidata.org/wiki/Q787177

Trac ticket: https://core.trac.wordpress.org/ticket/63586

​Toni Viemerö pointed out in Slack that there's an official API: ​https://downloads.mariadb.org/rest-api/mariadb/.

Use data from MariaDB API and re-enable test.
This patch assumes that when a release is missing from said API, it'll be EOL.

#9009 for MariaDB API

Thanks a much better idea, thanks folks.

[peterwilsoncc]

In 60329:

Database: Reinstate test for MariaDB version in readme.

Updates the test to use the MariaDB REST API endpoint of supported versions. A version is considered EOL if it has passed the listed date or is not included in the API response.

Follow up to [60313].

Props desrosj, johnbillion, skithund.
Fixes #63586.