tests: check that every check has a message for every return type and messageKey

[straker]

This will check that every time a checks unit test is run, it verifies that there exists a message for the return type, also taking into account how none checks use the opposite messages (e.g. a result of true will use a fail message). It will also verify that if the check has a data.messageKey property, that a specific message exists in the messages for that key.

Doing this revealed that we should combine the non-empty-if-present and non-empty-value checks as the fail state for what it's looking for (the state of the value attribute) produces a double message about the attribute:

"Fix any of the following:
  Element has a value attribute and the value attribute is empty
  Element has an empty value attribute
  ..."

Also made sure no pass result had a message key it didn't use in color-contrast (which seems to have run prettier on the file so that's why all the changes)

Closes issue: #3173