[Requests and ideas] Make automation cards easier to scan and toggle enabled state

## Problem
On the Automations page, it is hard to quickly scan which automations are enabled versus disabled and to toggle that state without opening or otherwise inspecting each automation. Disabled automations currently show a badge near the top-right of the card, while enabled automations do not have an equally explicit state indicator. This makes mixed enabled/disabled lists slower to understand and manage.

I have no idea what's actually enabled/disabled, now is it easy/intuitive to toggle.

## Recommended UX
Add enabled/disabled controls to each automation card footer:

- Put an enabled/disabled toggle on the bottom-left of the card.
- Show the current state beside or integrated with that control, e.g. "Enabled" / "Disabled".
- Keep the control visible in the same place for both enabled and disabled automations so the list is easy to scan.
- Preserve the existing run/action affordances on the right side of the footer.

## Suggested behavior
- Toggling updates the automation enabled state inline from the card.
- The card state updates immediately after a successful change.
- If the update fails, surface the existing error pattern and restore the previous toggle state.
- The control should be keyboard accessible and expose a clear screen-reader label, such as "Enable automation: {name}" or "Disable automation: {name}".

## Why this helps
This would make the Automations page faster to use when managing several automations, especially when reviewing a mixed list of active and disabled schedules. A consistent bottom-left state indicator plus toggle would make status scannable and reduce the number of steps required to enable or disable an automation.

Start at the Automations page and inspect the automation card, including the existing disabled badge and footer run/action controls. Add a consistent enabled/disabled control in the bottom-left, preserving the existing footer actions, then verify inline success updates, failure recovery, keyboard access, and a clear screen-reader label for each automation.

Written by the indexing model from the issue text.