save/load infoSettings Struct instead of save/load every variable individually, Fix Screen freezes/Click to Resume message/damaged M105 command in Marlin mode

[guruathwal]

• The settings are stored in the last 2KB of the program memory. earlier a separate entry was used to save/ load each variable. With this the infoSettings Struct is copied at once to/from buffer instead of saving/loading every variable individually, removing the need to add save/load entries for each variable. This also eliminates bug related to wrong/invalid settings being loaded. The prebuild settings size check now works accurately.
• Add missed level_edge_distance ([Q] Option "level_edge_distance: #1467)
• Prevent initial gcode queries when not in touch mode (This may be causing freezes due to long M503 response and other initial gcode responses when the TFT boots in marlin mode.)
• Fix Screen freezes in Marlin mode ([BUG] Screen freezes in Marlin mode while starting to draw status screen. #1433) cause by serial connection not getting initialized while booting in marlin mode after PR Fix: temperature auto-report timeout check, Fix invalid settings parameters #1438).
• Fix Click to Resume" message in marlin mode ([BUG] Click to Resume on startup in Marlin Mode (serial_always_on:1) ? #1383) and "damaged M105 command" ([BUG] Today's merger of PR has created new problems. #1297) caused by M105 delay set to 0 in PR Temperature update when printing from onboard SD #1244.
• Cleanup Configuration.h

Fixes #1433 , fixes #1383, fixes #1297

[digant73]

please remove config.ini. I already merged your changes (you reported in this PR) in mine. Have a look to my PR and let me know if something is missing

[rightawy]

@digant73 you should not ask anyone to remove there work and copy it to yours.

[digant73]

@rightawy it is pretty much useless to provide something that was already added in an existing and specific PR and that was also notified in the related bug.

[oldman4U]

Good to see that we do not have enough bugs to fix and open feature requests, so that several developers are working on the same topic again.

Just as a reminder: #1170 and #1218 ;-)

Thank you