[MRF-3] PLU-520: introduce mrf action that cannot be added by user

[pregnantboy]

Changes

• Created a new hidden action mrfSubmission for FormSG app that handles subsequent MRF submissions
• Added validation to prevent users from creating or updating hidden actions
• Updated GraphQL schema to include hiddenFromUser property for actions
• Added a helper method in App model to find triggers or actions by key
• Modified the frontend to filter out hidden actions from the UI

How to test?

• Add step modal should not show FormSG action
• Comment out the frontend filter, and try adding formsg action -> it should fail

What's not done?

• Preventing reordering of hidden actions
• Preventing deletion of hidden actions
• Preventing step name change of hidden actions

[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
• [MRF-3] PLU-520: introduce mrf action that cannot be added by user #1266 👈 (View in Graphite)
• [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: c19785a | Docs | Was this helpful? Give us feedback!}

[linear]

PLU-520 MRF: Approvals

[kevinkim-ogp]

lgtm!
✅ cannot add or update hidden actions via UI or graphql