[Improve] Keep custom automation controls available during run now

[roomote-roomote]

Created by Roomote. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

• Give each custom automation run button independent mutation state, so enqueueing one run does not disable creation or other run buttons.
• Include the automation name in launched-task toasts for custom and built-in automations.
• Use the consistent Running {automationName} now message with a View task action.

Why this change was made

Enqueueing a custom automation previously participated in a section-wide busy state, blocking unrelated automation actions while the request was pending. Run-now feedback also did not consistently identify the automation that launched the task.

Impact

Users can create or run other custom automations while one run is being enqueued, and launched-task notifications clearly identify the automation with a direct task link.

[roomote-community]

No new code issues found. See task

_{Reviewed 6586138}