Warn of mismatch between helicity pattern size in config files and data stream

[paulmking]

If the size of the helicity pattern as used in the data stream is smaller than the size of the pattern the analyzer is expecting (for instance, the analyzer is trying to decode octets, but the data is in quartets), it will not provide any warnings, nor will it build valid pattern data.
We need to have a warning so we know we have a mismatch.

I'm pretty sure the contrary case will give a warning, but it should also be checked.

[paulmking]

This can be tested with the mock data file by changing the PatternPhase setting in mock_qweak_helicity.map to either 2 (to expect pairs) or 8 (to expect octets). The mock data files seem to always be generated in quartets, so running qwparity on a mock file with parits or octents should give clear errors.

[paulmking]

It would probably be good to have the program exit after "a few" failures to find the type of pattern that was asked for.