Consider composer validation commands about laminas-ci-matrix-action

[Ocramius]

Prior to running composer install

I really want this sort of stuff in independent jobs, not in "before" or "after" scripts.

Having to jump in a failed PHPUnit job because something completely unrelated failed is no fun :D

[internalsystemerror]

Good idea, I should probably transfer this to the matrix action repository.

[internalsystemerror]

Hmmm... My original thoughts for adding this to the integration action are because if composer install fails, I'm not sure it will then proceed to composer validate in order to get more information as to why it failed. But the information given is an assumption, I intend to do some testing to see what benefits composer validate could bring us over a simple install.

As it relates to the composer check-platform-reqs command, having this as a separate job would mean that a new job would need to be created for each option in the matrix (7.4-lowest, 7.4-latest, 7.4-locked, 8.0-lowest, 8.0-latest, 8.1-lowest, 8.1-latest).

[internalsystemerror]

Also adding composer audit for consideration (issue description updated)