[CI] Test matrix: remove php7.3, mysql5.7.

[rosiel]

GitHub Issue: #885

Discussion on Slack: https://islandora.slack.com/archives/CM5PPAV28/p1658234802046979 (no replies yet)

What does this Pull Request do?

Updates the testing matrix

What's new?

• instead of drupal 9.3.x and 9.4.x-dev, test 9.4.x and 9.5.x-dev
• instead of testing php 7.3, 7.4, 8.0, and 8.1; only test 7.4, 8.0 and 8.1. Drupal 9.4 has dropped support for 7.3.
• instead of allowing failure on php 8.0 and 8.1, make those mandatory.
• instead of testing on mysql 5.7 and 8, only test on 8. (isn't our DB work handled by Drupal's DB abstraction layer anyway?)
• remove testing Drupal 10 (breaks always)
• Update the badge on the README to say php >= 7.4

How should this be tested?

• Do these tests pass?
• Are they good versions to test?
• Is the new declaration ok? (I personally think having the badge match the testing makes sense, though i'm pretty sure our php )

Documentation Status

• Does this change existing behaviour that's currently documented?
• Does this change require new pages or sections of documentation?
• Who does this need to be documented for?
• Associated documentation pull request(s): ___ or documentation issue ___

Additional Notes:

Any additional information that you think would be helpful when reviewing this
PR.

Interested parties

Tag (@ mention) interested parties or, if unsure, @Islandora/8-x-committers

[rosiel]

After thought and discussion with @alxp , it's probably more useful to use tests to look forward (even if they fail, as they do, on our dependencies like Stomp isn't yet PHP 8.1 friendly and Contexts won't install on D10), rather than have the nice green checkmark in the pull request list 😢. So...

• PHP 8.1 is in the matrix but as allowed_failure.
• Drupal 10.0.x-dev is in the matrix but only on PHP 8.1

In order to make it easier for PR reviewers to understand the test output, we can use the Branch protection's "required tests" - they show up with a special "Required" badge, and I guess we can use that to evaluate if the PR is ready to merge.

(we'll need to change the required tests for this PR to be merged)

[rosiel]

It might be time to update the rest of islandora's testing matrices too. I propose:

• let's stop testing php 7.3
• let's add php 8.0 and 8.1 where missing
• for drupal modules, let's test D9 as 9.4.x and 9.5.x-dev (with intention to update this matrix as new versions release).

Open questions for Drupal:

• Should we include drupal 10.0.x-dev in the matrix expecting it to fail?
• MySQL 8 is out. Should we add it? and/or replace 5.7?
• Should we update modules still testing on D8 to 8.9.20 (from 8.9.11)?

[rosiel]

Discussion from the tech call:

• Drupal 9.3 is still supported till the end of the year. Leave it in.
• php 7.3 is ok to drop. 8.0, 8,1 ok to add.
• there are some drupal issues with mysql 8.0: https://www.drupal.org/project/issues/search?issue_tags=MySQL%208
• probably don't need 2 versions of sql. will use 8.0 to be future-ready
• time to deprecate Drupal 8.

[rosiel]

I finally went with my conscience, and removed php 8.1 and drupal 10 since we haven't had a chance to actually address them yet, and made issues about what we know so far. This way,

• we don't have jobs in the PR checks falsely marked as passing (it takes a lot of digging from the PR screen to see errors)
• we don't have the PRs and the CI badge marked as failing. I think that's too discouraging to be useful.