Add support for multiple Klipper instances

[Nojwe]

• Automatically discover all Klipper instances in $HOME following the pattern printer_data or printer_[instance name]_data
• Prompt user to select discovered instances for backup to github. Selected instances will be added to the .env file.
• Default to backing up the entire config directory; notes users can modify that by editing .env
• Allow user to select which Moonraker instance(s) to install the update manager on. Uses same instance list as the backup process
• Only restart specific Moonraker instance when the update manager is added

[Tylerjet]

@Staubgeborener I think you saw more about this in the issue that was open, I'll leave it up to you.
I believe you can already add the path in the current implementation so if this is just automating that process on install to find those paths and place them in the env, it seems good to me.

[Staubgeborener]

Unfortunately, I don't have the time to test everything at the moment, as I would need to set up an extra multi-instance for this. I'll keep it in mind and hopefully test it soon. If everything works, I'll merge it.

[Bradford1040]

Unfortunately, I don't have the time to test everything at the moment, as I would need to set up an extra multi-instance for this. I'll keep it in mind and hopefully test it soon. If everything works, I'll merge it.

I have worked on this on my fork I have it somewhat working! I would not say that it is a polished ready for an average user to install lol, FAR from it in fact! I just recently started working on it again, if I have something worth your time to look at I will speak up, my way of getting it done might not be the best course. I have a cron job for each printer and klipper-backup makes a /config_backup_<custom-name>/ directory and has been working on 8 different printers that I have on the same Klipper server (using a Dell PE730xd) not a R-PI.

This is the version am using that works but I have a few tweaks/fixes that still need to be addressed