New MaxValueValidator on NumberFilter triggers Decimal FloatOperation trap

[wearebasti]

The in 2.4.0 introduced MaxValueValidator sets as default 1e50 leading to have a float as max value, but the NumberFilter uses a DecimalField as base leading to FloatOperation exceptions if the corresponding trap is activated on the Decimal context. (https://docs.python.org/3/library/decimal.html#decimal.FloatOperation)

This is not visible for most people, I guess - we've it on in our test/dev-setup to not mix Floats and Decimals. I assume the max-value should either be a Decimal itself? (or a int(1e50) would probably suffice already.

In [2]: type(1e50)
Out[2]: float