fix(schedule): run missed scheduled tasks when the machine becomes available

[AsterZ99]

Summary

Improves the reliability of scheduled tasks that are created via WindowsScheduleManager (used by OK-WW's "Task Schedule" tab).

When a scheduled task is set with StartWhenAvailable=false (the current default injected into the task XML), Windows skips the run entirely if the machine is asleep or powered off at the scheduled time. For daily tasks like "run the farm routine every morning", this is the main reason a task is silently missed the next day even though the schedule is registered and "ready".

This PR flips the generated XML setting to <StartWhenAvailable>true</StartWhenAvailable>, so a missed trigger (e.g., the PC was asleep at the trigger time) is executed once the machine becomes available again.

Why this is separate from the "manual refresh" symptom

Opening the Schedule tab already triggers a force_sync (ScheduleTaskTab.load_tasks → on_refresh → query_all_tasks(force_sync=True)) that re-reads the OS. The OS-level trigger is independent of that UI cache, so a registered and enabled task WILL still fire the next day — the refresh only affects what the UI displays. The real reliability gap is the power-state skip, which this PR addresses.

Test plan

• Local python -m py_compile on ok/util/windows_schedule.py passes.
• Manual: create a daily scheduled task, verify the generated \Task\Settings\StartWhenAvailable element is true (e.g. via schtasks /Query /XML).

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud