Cleanup rotation code & triggers

[mastercactapus]

What problem would you like to solve? Please describe:
A lot of rotation code (particularly around editing) depends on a complex set of DB triggers that cause various issues around lock contention, races, etc...

Describe the solution you'd like:
Move the logic out of DB triggers and into the application.

Describe alternatives you've considered:
Continue to use exclusive locks everywhere we touch rotations.

Additional context:
Current list of triggers:

fn_set_rot_state_pos_on_active_change
trg_enforce_rotation_participant_limit
trg_enforce_rot_part_position_no_gaps
trg_inc_rot_part_position_on_insert
trg_set_rot_state_pos_on_part_reorder
trg_incr_part_count_on_add
trg_start_rotation_on_first_part_add
trg_10_decr_part_count_on_del
trg_20_decr_rot_part_position_on_delete
trg_30_advance_or_end_rot_on_part_del

As the current/older application code will still depend on these, we can't remove them completely (yet). Each trigger should be replaced with identical code, but with a short-circuit check of a local variable at the beginning. If the variable is set, the trigger function should return with no action taken. New code can set the local variable to disable the triggers in a tx, without affecting actions from older versions of GoAlert.

[stale]

This issue has been automatically marked as stale because it has not had recent activity.

[mastercactapus]

Closing as obsoleted by:

• proposal: Merging Schedules and Rotations #4084
• Migrate Rotation Manager to Use the New Job Queue System #4244