Various cosmetic changes and formatting

[classicrocker883]

Description

Mostly cosmetic changes, basically just hit Format Document and made tweaks

• Update spacing, syntax, comments, capitalize, spacing, and such to match likeness in code
• • This helps simplify code and adds better readability

Format:

• Reformatted many Python (.py) script files (for spacing and readability):
• • buildroot\share\scripts
• • buildroot\share\PlatformIO\scripts
• • src\lcd\extui\ftdi_eve_touch_ui\ftdi_eve_lib\scripts
    Also updated comments, such as "help" and usage:, when running the script in a terminal

Some rearranging:

• Fix runout/filament sensor spacing
• Rearrange: marlinui.h, planner.cpp, creality/dwin.cpp
• Arrange print_heater_state/s() in temperature.cpp to be inline with Temperature sensor IDs (src\inc\Conditionals-4-adv.h)

Added:

• Group *** BARICUDA *** - gcode.h
• Use GET_TEXT_F and MSG_... from language_en.h instead of literal Strings in CrealityUI dwin.cpp, which was a TODO:

Removed:

• Remove redundant code:
• • Remove double nested #if ENABLED(AUTO_BED_LEVELING_UBL) from settings.cpp

Move from other PR

Updated fwretract.h|fwretract.cpp

• Arrange/improve values + comments
• M208 was missing seenval, which is used in M207 companion
• Rearrange fwretract_settings_t struct to follow gcode example

Requirements

Benefits

Configurations

Related Issues

[thinkyhead]

Arrange print_heater_state/s() to be inline with Temperature sensor IDs

The multi-hotend states are sorted to the end for the convenience of hosts to get the current hotend and bed temperature in the early part of the string, so those should not be moved to the front or rearranged based on the arbitrary order of heaters in the configuration files or elsewhere.

[classicrocker883]

@thinkyhead ok I reverted that part in temperature.cpp

I added a couple changes in the planner files which were missed in the recent merge commit.

the only thing i'm not so sure about it utility.h - IAXIS_CHAR, is that fine or should be reverted?