Weird slicing behavior when close to X limits

[mkrumin]

If bladeXposAtSlideEnd parameter in systemSettings.yml is close to the maxPos of the X stage in componentSettings.m (which will result in the cutting to go beyond the maxPos of X) will result in buggy slicing behavior:

• the Cut Size (mm) will adjust correctly to honor the maxPos (so it will aim to not exceed maxPos X)
• however, the actual slicing might not happen. When doing Slice N Times it might just raise the z-stage, start the vibratome and then skip immediately to shaking of the Y-stage, without traveling in X. Same for Auto Trim and same for the actual acquisition. On a small sample size it does decide to fully cut once out of 3-4 slices, on the rest of the slices it just raises the z-stage.

Specific example, bladeXposAtSlideEnd == 60.7, maxPosX == 62