Set a rule to the given status without content validation or engine undeploy.

Activating a rule — moving out of inactive / error into active or
experimental — requires a completed retro run for the rule's current version.
Trigger one with POST /rules/{rule_id}/runs; without it the call is rejected
with a 400. Deactivating is never gated, so a rule with no runs can always be
set back to inactive.

A rule whose stored content no longer validates cannot be deployed at all: it has
no runnable SQL, so activating it would only re-create the state the automatic
quarantine demoted it out of. Fix the content first (the -- ERROR: banner must be
removed for the save to be accepted), then run, then activate.