Deal with rules that will never match because of 'X no X'

[ClementSparrow]

See increpare/PuzzleScript@3eb47fa.

For now I will just throw a warning, but I need to improve the error message by saying what object is the X and what entity is creating the no X. Also, it might be better to remove the rule as increpare does (but not silently: the existence of such a never-matching rule is a symptom that something is wrong and the dev should be warned about it).

[ClementSparrow]

The current implementation seems to throw warnings when it's not strictly necessary. An example from Vertebrae:

late up [ rayU | rayBlocker no DartWallD ] -> [ | rayBlocker ]

because DartWallD is a member of the property rayBlocker, and this property is not on a single layer, so it's expanded for all its members, which gives the expanded rule:

late up [ rayU | DartWallD no DartWallD ] -> [ | DartWallD ]

This is another case of #21, also related to #20.