🐛 Fix #201: Always allow submatches for combinations involving command

[greena13]

Context

When the Cmd (Meta) key is pressed down with other keys, it hides their keyup events, and only the Meta key keyup event is triggered. react-hotkeys accounts for this and simulates the keyup events for all the keys Meta was pressed down with, when the its keyup event is detected.

However, if you hold down Meta with another key, release the other key and press a third key while Meta is still down, react-hotkeys does not know the first key has been released until you also release Meta. So for example, if you press Meta down, then a, then release a and press b - react-hotkeys thinks you're still holding Meta+a+b until you release Meta. This is undesirable, but (so far as I can come up with) unavoidable, and generally does not cause problems.

When it does cause a problem is if you have actions for both Meta+a and Meta+b: the second action is never triggered. This used to work through submatching: Meta+a+b would still match an action bound to Meta+b. However, v2.0.0-pre7 introduced a new configuration option allowCombinationSubmatches (which is false by default) to address the multiple issues submatches were causing (#161, #181, #175), that disables this. And so we arrive at #201.

This pull request

• Ignores the allowCombinationSubmatches when Command is currently pressed

[greena13]

⬜️ Make this test specific to Cmd