Fixes the bug where you could always clear the input even if the limit were preventing you to do so (the last valid value was then set back on blur).Simplify the min and max range tests with the new private _isWithinRangeWithOverrideOption() function.
For information, the overrideMinMaxLimits doNotOverride is still the default behavior. From now on, whenever the user sets a minimumValue higher than 0, or a maximumValue lower than 0, a warning will be displayed in the console telling him to perhaps use the overrideMinMaxLimits invalid option.Beware To reduce complexity, the 'autoNumeric:invalidValue' event as well as the 'autoNumeric:minExceeded' or 'autoNumeric:maċxceeded' events are now sent up to three times for a single input on keypress, keyup and blur.When the value is corrected, the new 'autoNumeric:correctedValue' event is sent. Whenever the user type an invalid number (out of range), the new 'autoNumeric:invalidValue' event is sent.Do note that contenteditable-enabled elements cannot have a validity state set, so AutoNumeric instead sets by default the an-invalid CSS class on such 'invalid' elements.Users can then target the CSS :invalid and/or :valid state as they wish to display a visual feedback as needed.While in this out-of-bound state, the element validity status is set to invalid.This allows users to type temporary invalid numbers when the minimumValue is superior to 0, or the maximumValue is inferior to 0.Fixes #543 Allow users to enter out-of-bound numbers, outside of the minimumValue and maximumValue range.