Always have a PHP and TYPO3 version matrix for the PHP-related CI jobs

[oliverklee]

Story

As a developer, I want to always have the used PHP and TYPO3 versions in the CI matrix (for jobs that do a composer install/update) so that I know which PHP and TYPO3 versions are used.

As a developer, I want the CI jobs to be build as consistently as possible so that maintenance is easier.

As a developer, I want the CI jobs to have the some matrix structure so that Composer caching works across jobs.

Acceptance criteria

• The php-lint job also has a TYPO3 version matrix.
• The code-quality job has a PHP and TYPO3 version matrix.
• The static-code-analysis job has a PHP and TYPO3 version matrix.
• These jobs also have the min/max dependencies Composer matrix entries.
• These jobs pass these matrix entries when doing the composer update.
• It is documented in the PHP and TYPO3 version entries in the matrix that these must match the default versions in runTests.sh.
• It is documented in the code in runTests.sh that the versions in the CI jobs need to be changed when the default TYPO3 or PHP version is changed.

Additional information

Documentation on the GH action matrices