Functionality for creating new session or resuming/restarting an existing session

[biyeun]

Technical Summary

• adds utility to check if an existing case bulk edit session exists
• adds utility to check if an existing form bulk edit session exists
• adds utility to create a new case bulk editing session, including default columns and pinned filters
• adds utility to restart a case session (delete old session and start a new one)
• adds tests

new UI additions:

Feature Flag

DATA_CLEANING_CASES

Safety Assurance

Safety story

safe change, does not affect production workflows

Automated test coverage

yes

QA Plan

Not needed

Rollback instructions

• This PR can be reverted after deploy with no further considerations

Labels & Review

• Risk label is set correctly
• The set of people pinged as reviewers is appropriate for the level of risk of the change

[nospame]

Nothing major, but a couple of questions that I would feel more comfortable knowing answers to before approving

[nospame]

Since we already know from test_has_no_active_case_session_after_committed that the session won't be active after it's committed, it's not clear what adding a completed_on is doing here.

[biyeun]

there will never be a state where completed_on is set, but committed_on is null. it's just mimicking that state

[nospame]

That makes sense in trying to mimic a real state, but to me it means this test isn't adding value, since we can't tell whether adding completed_on is doing anything. I don't find it blocking, as it's probably a good test case to consider, but worth thinking through what is the testable distinction between just having committed_on set, and having both committed_on and completed_on set.