Add restore dietpi.txt option

+ DietPi-Software | Add way to automatically restore from backup on first boot

+ DietPi-Software | CodeFactor fixes

+ DietPi-Software | Make mawk more specific

+ DietPi-Software | Various fixes

+ DietPi-Software | Remove other instance of $BACKUP_STATS_FILENAME

+ DietPi-Software | Syntax Fixes

+ DietPi-Software | Fix alist syntax error

+DietPi-Software | Boot into normal DietPi after restoring backup

+ DietPi-Software | Fix booting into normal DietPi

+ DietPi-Software | Don't change install state and sync filesystem

+ DietPi-Software | Switch from sed to G_CONFIG_INJECT

Update restore-boot branch

+ DietPi-Software | Fix automatic restore

…o restore-boot

+ DietPi-Backup | Fix search function

+ DietPi-Software | Only reboot if backup succeded

+ DietPi-Software | Auto-restore backup: Reformat code (remove doubled indentation and such)
+ DietPi-Software | Only reboot when backup restore succeeded, inform user about it for three seconds
+ DietPi-Software | Downgrade auto-restore =2 to =1 in every case

+ DietPi-Software | Syntax: We are not in a function

+ DietPi-Software | On first run installs, services are disabled already, hence skip stopping and especially restarting them after restore has completed, as a reboot is done immediately.

+ dietpi.txt | Add info that all attached drives will be mounted and searched automatically when restoring backup on first boot

+ CHANGELOG | DietPi-Backup: A new feature has been added which allows to automatically restore a dietpi-backup on first boot

+ DietPi-Backup | Clear PATH cache after backup restore, in case commands are restored to a different locations

+ Update restore-boot branch

+ DietPi-Backup | Do not stop services before we definitely run the backup or restore. The rsync process check still needs to be done after stopping the services, which include the rsync daemon. But do not kill a running rsync process afterwards, better error out.
+ DietPi-Backup | Implement a first function when restoring a backup, to check whether the backup's UUIDs match the current drive's UUIDs, so that we do not restore a system that is not booting, because the bootloader and fstab do not find the configured drives. If the UUIDs seem to not match, check whether we are able to reliably make the system bootable by adjusting known bootloader configurations. Add function to restore UUIDs, in case, but content is on ToDo for now :).

+ DietPi-Globals | G_WHIP_YESNO: If the default is set to "yes", return "true" as well in case of non-interactive calls

+ DietPi-Backup | Restore now obsolete functions
+ DietPi-Backup | Satisfy shellcheck
+ DietPi-Backup | Add whiptail yes/no dialogues when storing a backup to a system with different UUIDs. Default to "yes", if we did find the boot configuration method, else default to "no", which is especially relevant for non-interactive first run setups with AUTO_SETUP_BACKUP_RESTORE=1 set.

+ DietPi-Backup | Full function to update UUID entries in fstab and boot configs after restore, if required

+ DietPi-Backup | Satisfy shellcheck

+ DietPi-Drive_Manager | Fix grabbing input argument

+ DietPi-Backup | Fine tune output, coding and order of service start/stop and interactive parts

+ DietPi-Backup | Tiny

+ DietPi-Backup | Fix SBC boot config estimation and avoid doubled fstab rootfs edit as the loop includes root as well