[MRF-4] PLU-520: automatically create/delete/update mrf steps on check step

[pregnantboy]

What changed?

• Created a new function createMrfSteps
  • Handle creating of the new MRF steps on Check Step
  • It should handle deleting/updating and adding of MRF steps while maintaining positions of other steps
• Updated the FormSG new submission trigger to detect multi-respondent forms and create the appropriate workflow steps

How to test?

1. Create a new flow with a FormSG trigger connected to a multi-respondent form
2. Verify that the MRF workflow steps are automatically created with the correct parameters
3. Update the form's workflow and verify that the steps are updated accordingly
4. Test different scenarios: adding new steps, removing steps, and updating existing steps

[pregnantboy]

Warning

This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

• [MRF-8] PLU-520: New Approve-Reject component (frontend) #1284 : 2 dependent PRs (#1285 , #1349 )
• [MRF-7] PLU-520: remove mrf actions steps if necessary #1275
• [MRF-6] PLU-520: testStep for mrf actions should test multiple steps #1269
• [MRF-5] PLU-520: refactor frontend to allow test step on mrf actions #1268
• [MRF-4] PLU-520: automatically create/delete/update mrf steps on check step #1267 👈 (View in Graphite)
• [MRF-3] PLU-520: introduce mrf action that cannot be added by user #1266
• [MRF-2] PLU-520: parse formsg workflow data + refactor #1265
• [MRF-1] PLU-520: allow mrf forms to be connected #1264
• mrf/trunk

This stack of pull requests is managed by Graphite. Learn more about stacking.

[datadog-opengovsg]

✅ Tests

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: cb6a565 | Docs | Was this helpful? Give us feedback!}

[linear]

PLU-520 MRF: Approvals

[kevinkim-ogp]

nit: don't need await here

[kevinkim-ogp]

lgtm, tested and verified that these work!

• MRF steps are created and inserted correctly
• New MRF steps are added
  • Existing actions remain in the correct position
• Deleted MRF steps are deleted
  • Existing actions are collapsed below previous MRF step
• Updated MRF steps are updated
  • MRF step and existing actions remain in the correct position