Update deployment, some fixes to ota

[smarthomeagentur]

This pull request introduces significant improvements to the device selection and recommendation process for Canary OTA rollouts, focusing on stricter filtering for device recency, enhanced usability, and improved documentation. The most important changes are grouped below:

Device Recommendation Logic and Filtering:

• The recommendation algorithm now only selects devices that have been online within a configurable time window (default: less than 1 hour), making the rollout safer and more targeted (generate_recommendations, calculate_suitability_score, and related CLI changes). [1] [2] [3] [4] [5]
• Added a new CLI argument --max-age-hours to control the maximum age of a device’s last contact for recommendations, with all relevant logic and documentation updated accordingly. [1] [2] [3]

Usability Improvements:

• Added a new function that prints copy-paste ready device ID lists and CLI commands for quick rollout and monitoring, improving workflow efficiency for operators. [1] [2]
• Markdown and JSON outputs now clearly indicate the recency filter applied to candidate devices.

Documentation and Template Updates:

• Updated the documentation and template generation to clarify filtering criteria and ensure consistent timestamps and placeholder handling. [1] [2] [3] [4] [5]

Firmware Update Handling:

• Improved OTA update routines to handle display and power supply state more robustly before and after firmware updates, and added error logging if an OTA attempt fails. [1] [2] [3] [4]

These changes make the Canary rollout process more reliable, transparent, and user-friendly.