[MRF-6] PLU-520: testStep for mrf actions should test multiple steps

[pregnantboy]

Changes

• Modified execute-step to execute testRun for all MRF steps
• Updated the action processing to properly handle metadata from MRF submissions
• createMrfSteps should replicate the connectionId for all steps created

refactor

• Created a schema validation for MRF workflow steps
• Removed the mockDataMsg field from trigger instructions, hardcode on frontend instead

How to test?

1. Connect an MRF form
2. Click check step on any of the MRF steps, all fields should appear together with the mock data message
3. Verify that all MRF steps are properly connected and share the same connection ID

What's not done?

• Filtering only editable fields for each step

[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 👈 (View in Graphite)
• [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
• [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: 4781dbc | Docs | Was this helpful? Give us feedback!}

[linear]

PLU-520 MRF: Approvals

[kevinkim-ogp]

do we need this metadata here?
may be missing something, but seems to be redundant

[kevinkim-ogp]

• Check step and all fields appear with mock data message
• MRF steps are connected to the same connection id
• Check step with real submission 👈 can't check step with real submission data (if this is meant to be the case for this PR, can ignore this)

note for checking with real data: need to use formSgSdk.cryptoV3.decrypt for MRF