Mesh with BABYSTEP_ZPROBE_OFFSET: add sanity check

Apply maths macros and type changes ahead of HAL

Use the raw position for mesh measurement. Otherwise the `M206` and
`M92` Z offsets will get canceled out by bed leveling. The downside is
`G29` will not compensate for a poorly set small `M206` fudge value.

To elaborate on this issue, imagine you are probing with a Z home
offset of -0.1, meaning when Z homes, -0.1 is the current position,
implying the ideal bed zero for the nozzle is 0.1mm higher than the Z
endstop. Ordinarily when printing, Z would raise 0.1mm higher.

What happens when we probe is that all points are measured with that
-0.1 included. So when bed leveling is enabled the `M206 Z` offset gets
exactly canceled out by the bed readings.

Step-by-Step Menu addition

- Fix: When "100.0" changes to "99.0" the LCD shows "199.0"
- Use 2 rows if needed on character LCD, (allowing longer labels…
Germany, et. al.)
- Known issue: A certain length label combined with a certain value
drawing function could, for example, display 99.0 on 1 line, but 100.0
on two lines. Workaround would be to pass a nominal value size argument.

Convert DAC percent to uint8_t

* Add Z Fade Height to M420 Output

Echo the z-fade height when M420 is called, if it is enabled.

* Fix Whitespace

* Fix Compiler complaint

* Missing semi-colon

=====================

add test to Travis

Support for two switching extruders

Fix #5699 - LIN_ADVANCE freeze when ADV_RATE returns 0

Fix Italian language mapper

I2C Position Encoders Example Configs

Added missing Italian translations

M600 fixes

Addressing #7057

Move lcd_refresh_zprobe_zoffset definition

Fix status message, apply #7058

Thursday cleanup / bugfixes

PCA9632 PWM color LED support