Nested calls to snap methods in Region give different results

Region has snapSizeX and snapSizeY methods that use Math.ceil, and depending on numerical errors, calling them twice can lead to different results, but when snapping an already snapped value (either intentionally or by mistake), the result should be the same, otherwise we'll be jumping unnecessary from a valid pixel to another pixel.

This error can be found for instance on Windows with UI scale 175%. Some controls like the CheckBox, are laid out with ellipses as a consequence of wrong calculations.