Order total range condition

Slight changes to patch #24. Changed states to make new fields not required when they're not shown. That should fix the saving issues reported in #25.

I think you should use commerce_price form elements instead of number, patch attached.

Latest patches no longer seem to apply to 2.37.0

Updated patch for Commerce 2.37.0

RangeConditionTrait is used for both OrderTotalPrice and OrderItemQuantity. In OrderTotalPrice min_value and max_value are Prices. In OrderItemQuantity min_value and max_value are numbers.

In #33 RangeConditionTrait was changed from using numbers to using Prices, resulting in OrderItemQuantity no longer working correctly.

Changing back to number.

Well this RangeConditionTrait is not really a trait, as it only works for either total amount (#35) or total quantity (#37).