Class RevertInteractiveFormAction

Revert the user's Active override to an older Component version. Pure re-point: no new Component is created, no new Override row is created.

Behaviour:

• Identify the Active Override for the (entity, user) — we either take it from the input ActiveOverrideID if supplied, or look it up using the target Component's EntityID.
• Identify the target Component to revert to — by TargetComponentID or by TargetVersionSequence (relative to the Component lineage sharing the same Name as the currently-active Component).
• Set Active Override's ComponentID to the target → save.
• Flip the previously-pointed Component to Status='Inactive', target Component to Status='Active'.

The override is saved first. Both Component status saves are then tried, even when the first fails. If either fails, or the target Component cannot be loaded for its status save, the action returns PERSIST_FAILED that names every Component whose status was not updated; the override stays re-pointed. The override then already points at the target, so a retry with the same target returns SUCCESS from the no-op path and the Component statuses stay as they are.

Old Component rows are never deleted — they remain as immutable history. A subsequent revert can move forward again to any version.

Only the caller's own User-scope overrides can be reverted. A Role or Global override, or another user's, returns FORBIDDEN for every caller (see CheckPersonalWrite in _shared.ts): shared forms are managed from Form Builder or the form's Manage drawer.

Inputs:

• ActiveOverrideID (required, string) — the Active override to re-point
• One of:
  • TargetComponentID (string) — explicit Component to revert to, or
  • TargetVersionSequence (number) — pick the Component with this VersionSequence in the same Name lineage

Outputs:

• OverrideID — echoed
• ComponentID — the newly-Active component
• PreviousComponentID — the component we demoted
• Version — version string of the now-Active component