* Initialize mixing virtual tools to behave like standard a multi-extruder setup

* Update Marlin_main.cpp

* Update Marlin_main.cpp

Fix #8540

MK2_MULTIPLEXER does not require E2/E3 stepper pins

Does it?

[1.1.x] Adapt MESH_EDIT_GFX_OVERLAY

[1.1.x] Added optional NanoDLP Z movement synchronization

Addressing #8544

Implemented synchronization message output for NanoDLP printers (nanodlp.com).
If optional feature is enabled in `Configuration_adv.h`, Marlin will ouput "Z_move_comp" string to serial after completing any G0/G1 Z-axis movements. This feature patched on previous versions(1.0) is used by NanoDLP to synchronize Z-axis movement with projector exposure in DLP stereolithography printers.

[1.1.x] Make G26 work with other meshes too

Example Configuration.h files are not updated yet.   You need to cross
your settings over to the default Configuration.h file in the \Marlin
directory.   (UBL_G26_MESH_VALIDATION enablement has moved to a new
location in the file.)

[1.1.x] Tool change bad behaviour fix

[1.1.x] Fix up LCD init / charset

For parity with bugfix-2.0.x

Just aligned with version 2.0. Here bug was not present

Followup to 13a3fb1acc

[1.1.x]  tool change bad behaviours

This PR will address two issues reported in #8492. Just one is left because I don't know if it is an issue or not

1) when no home is done ("no_move" is set) tool change should never move X & Y because... I don't know where I am...only Z should be adjusted to avoid bed collision if other nozzle is lower than current.
2) Since no move no bed level matrix should be applied
    When SWITCHING_NOZZLE is enabled and system is homed there are two movements to go to destination, but first can move Z to older position and then crash on the bed

[1.1.x]Update Anet A8 default values from my Anet A8 experience

[1.1.x] M43 end pin correction/compatibility

[1.1] No retroactive adjustment with M851 Z

This is a non-intuitive change.   @oldmcg says in this post https://github.com/MarlinFirmware/Marlin/issues/7572#issuecomment-340641207 that using DELTA_PRINTABLE_RADIUS is better than DELTA_PROBABLE_RADIUS for setting the probe limits.   This is because the automatic probe code checks all locations for being reachable by the probe prior to doing the probe.

[1.1.x] Fix PlatformIO dependencies

[1.1] gitignore visual studio update

[1.1] Fix FILAMENT_LCD_DISPLAY, disabled state, optimize

aligned with marlin 2.0 gitgnore to support visual studio  community edition