Add some detail for the 'Invalid Pattern' messages (issue #415)

Partially addresses issue #415.

Not the best solution - you can't see the valid data in the pattern, just a second line saying "BAD RECIPE". But I don't think a "valid=false" flag is very good, either. (Which the pattern terminal would attempt to ignore, and clear on re-encoding.) The problem with that is signaling the error condition to all the other consumers of `ItemEncodedPattern#getPatternForItem()` (such as the crafting CPU) which shouldn't have to deal with bad patterns.

See https://github.com/AppliedEnergistics/AppliedEnergistics-2-Localization/pull/84
better use enums here. `public static final int` will not scale and its error prone, cause not really type safe.