Feature Request: Add --run-script-at-startup option (triggered on OS boot and system resume/wake)

Currently, Duplicati provides options like --run-script-before and --run-script-after which are tied to individual backup jobs. However, there is no built-in way to execute a custom script globally before Duplicati starts processing tasks for the first time after the host operating system wakes up from sleep/hibernation or a reboot.

For users running Duplicati as a continuous background process (e.g., TrayIcon on Windows), devices often enter Sleep, Hibernate, or Modern Standby rather than doing a full reboot. When the system wakes up, certain prerequisites (such as waking up a NAS via Wake-on-LAN, mounting network drives, establishing a VPN connection, or initializing cloud storage mounts) need to be handled before scheduled or missed backups immediately kick in and fail.

I would like to propose a new global option (or advanced setting), such as --run-script-at-startup (or --run-script-on-wake), that triggers a specified script in the following scenarios:

  1. When the Duplicati server/application initially starts (e.g., on OS boot/login).
  2. When the host OS resumes from Sleep, Hibernation, or Modern Standby (e.g., listening to SystemEvents.PowerModeChanged / PowerModes.Resume or display wake events on Windows, and equivalent power management signals on Linux/macOS).

Ideally, this should also include an optional delay or blocking behavior (similar to --run-script-before-required), ensuring that queued/missed backup jobs wait until the startup/wake script finishes executing before starting.

Having this handled natively within Duplicati would greatly improve reliability for laptop and desktop users who rely on sleep modes and external/networked backup destinations.