Handle properly coordinate overflow in Marlin Renderer

Marlin (like Pisces) does not check input pixel coordinates (as float) for possible overflow:
- NaN, +/- Infinity
- abs(x|y coord) > UPPER_BND

Besides, it should also check that subpixel coordinates remain in the valid range too (even after applying the affine transform).

It can lead to possibly generate artefacts.
Moreover, it could also provide performance benefits:
- FloatMath.ceil / floor (could skip NaN / Infinity checks)
- avoid several overflow checks in the Marlin rendering pipeline

See sun.dc.DuctusRenderingEngine#feedConsumer(...) for the Ductus implementation of such filter