Power Schedule: tag-based resources, RDS/Aurora, days_of_week triggers

[joelgaria]

Description

Extended Power Schedule with the following capabilities:

• Tag-based resource discovery (AWS only): resources matching configured tags are powered on/off automatically, without manual assignment. The tag filter is configured via Add Resources To Schedule, where a dedicated "By tags (AWS)" tab allows selecting tags and resource types. The resource list refreshes every minute to pick up changes made directly from the cloud console.
• Ordered startup/shutdown: on shutdown EC2 instances are stopped first, then RDS — on startup RDS is started first, then EC2, to avoid application errors.
• RDS Instances and Aurora Clusters: added AWS API calls to start and stop RDS instances (start-db-instance / stop-db-instance) and Aurora clusters (start-db-cluster / stop-db-cluster), with polling until the resource reaches the available/stopped state.
• Current instance state: the schedule detail view shows whether each resource is running or stopped, including intermediate states (stopping, pausing, resuming, pending) during transitions.
• days_of_week per trigger: each trigger can run only on selected weekdays.
• "Run now": executes the schedule immediately from the UI, regardless of the configured trigger times.
• Last run details: after each execution, the schedule detail view shows the outcome per resource — how many were started/stopped and any per-resource errors (e.g. resource not found, invalid state).

Tag filter configuration (AWS)

Resources discovered via tags

Schedule panel

Special notes

This contribution was developed with AI assistance (Claude Code).
Tag-based filtering queries AWS live (EC2/RDS describe APIs) and falls back to MongoDB for the list/count endpoint to avoid unnecessary API calls.

Checklist

• The pull request title is a good summary of the changes
• Unit tests for the changes exist
• New and existing unit tests pass locally