Add per-rule group execution and UI controls
Description
Introduces API and backend logic to execute individual rule groups, including endpoint, service changes, and tests. Adds a RunButton component and integrates execution controls into the RuleGroup UI, allowing users to trigger execution for specific rule groups and view execution status.
Checklist
- [x] I have read the CONTRIBUTING.md document.
- [x] I have performed a self-review of my code.
- [x] I have linted and formatted my code.
- [x] My changes generate no new warnings.
- [x] New and existing unit tests pass locally with my changes.
How to test
- Create a Rule
- Go to the Rules page
- You should see a new Run button next to the Edit button
Additional context
After clicking the Run button on a Rule, all other Run buttons are disabled while the Rule is executing.
I have just started looking into the PR, but I noticed the CSS needs to be tweaked on the Run button.
Was it intended to not respect the active or inactive status of a rule?
Closing this as the rule executor was rewritten in #2148 and this functionality has been delivered in #2173.