mwscript comparison operator handling is too restrictive

Operators like =>. =<. <>. <<. >>. >< are technically invalid, but in TESCS and thus OpenMW they mean what their first character means (i.e. ==, ==, <, <, > and > respectively) but this behavior is not specific to characters normally used by comparison operators, but rather any special characters including spaces up until the right operand of the expression which can be a number or a name. So things like <<, <& and <: should be handled the same way. This should be investigated to reduce the number of special cases our scanner has as it's very doubtful Bethesda had added special handling for all of the "operators" mentioned above.