Swap 5222 user office experiment workflow improvement

[yoganandaness]

This pull request introduces a major overhaul of the workflow data structures and migrates existing workflow data to the new schema. The changes are focused on improving workflow management, enabling more flexible graph-based workflows, and ensuring data integrity during migration. The update includes new tables, foreign key relationships, triggers, and migration scripts to transition all relevant data and references.

Schema redesign for workflow management:

• Added new tables: workflow_has_statuses, workflow_status_connections, workflow_status_connection_has_workflow_status_changing_events, and workflow_status_connection_has_workflow_status_actions to support graph-based workflows, status transitions, and associated events/actions.
• Updated the workflows table to include an updated_at timestamp, and renamed status_actions to workflow_status_actions for clarity.

Migration and data integrity:

• Created comprehensive migration logic to transfer existing workflow nodes, edges, actions, and events to the new tables, with checks for unmapped data and warnings for any migration issues.
• Updated references in proposals and experiment_safety tables to link to the new workflow graph, and added triggers to keep status_id in sync with the new workflow_status_id. [1] [2]

Cleanup and deprecation:

• Removed deprecated tables and sequences related to the old workflow system, such as workflow_connections, workflow_connection_has_actions, and status_changing_events, after successful migration.

Event and action handling changes:

• Events are now stored as strings in application code instead of a dedicated catalog table, simplifying event management and reducing schema complexity.

Referential integrity and constraints:

• Enforced new foreign key and unique constraints to ensure all workflow transitions and actions/events are valid and prevent duplication or orphaned records. [1] [2]

Description

Motivation and Context

How Has This Been Tested

Fixes

Changes

Depends on

Tests included/Docs Updated?

• I have added tests to cover my changes.
• All relevant doc has been updated