Should we be failing to run PHPUnit tests when coding standards and static analysis checks fail?

[stephen-cox]

When coding standards and static analysis checks fail we don't run the PHPUnit tests which can sometimes be a pain because the failures are very minor and it would be good to see the status of the PHPUnit tests when reviewing a PR at Merge Tuesdays.

Not running PHUnit tests saves running GitHub Actions, but we're not being billed for these so it's not a financial cost.

[millnut]

Happy to change this, however when reviewing PRs we need to ensure any code added is following Drupal's coding standards as well as passing PHPUnit tests