build: release v6.110.0

[justynoh]

New

• feat(mrf): retain workflow through a submission lifetime #7087
• feat(config): allow R2 bucket URLs #7097
• feat(mrf): frontend field locking #7091
• feat: payments thank you page preview and edit mode #6969
• fix(mrf): use undefined as default for response display #7095
• feat(mrf): dynamic routing #7078
• build: merge release v6.109.0 into develop #7085
• chore(dev): update README with clearer virus-scanner install instructions #7083
• build: release v6.109.0 #7081

Dependencies

• chore(deps): update ip package #7098
• build(deps): bump ip from 2.0.0 to 2.0.1 in /serverless/virus-scanner #7101
• build(deps): bump ip from 2.0.0 to 2.0.1 in /scripts/20230317_whitespace_issue #7100
• fix(deps): bump ip from 1.1.8 to 1.1.9 #7099
• chore(deps): fix synk vulnerabilities #7089

Dev-Dependencies

• build(deps-dev): bump ip from 1.1.8 to 1.1.9 in /frontend #7102
• chore(deps-dev): bump semver from 5.7.1 to 5.7.2 #7090

Tests

feat(mrf): retain workflow through a submission lifetime #7087
@kathleenkhy

• Create an MRF form without a workflow. The usual response link passing should still work, with all fields enabled for all respondents.
• Create an MRF form.
  • Create a workflow where step 2 is a static value a@gov.sg and step 3 is another static value b.gov.sg.
  • Submit the form once as Respondent 1. a@gov.sg should receive an email reminder to submit the form.
  • Now, change step 3 to be a different static value c@gov.sg.
  • Click the button in the email that a@gov.sg received to fill the form. Submit the form.
  • Check that b@gov.sg got the next respondent email, and not c@gov.sg.

feat: payments thank you page preview and edit mode #6969
@KenLSM
Payments Form

Ensure that design is updated in Edit mode

• Add a payment variable to a form
• Check that the Thank You page shows the latest design
• The Button text and Button redirect link should be disabled
• The text should still be within the Summary table if the product name is very long
• Upon clicking the Save proof of payment button, the page should be refreshed/ reloaded

Ensure that design is updated in Preview mode

• Click on the Preview (eye) button of the form in admin mode
• Check that the Thank You page shows the latest design
• The text should still be within the Summary table if the product name is very long
• Upon clicking the Save proof of payment button, the page should be refreshed/ reloaded

Thank you page happy flow with actual form

• Click on the share button to launch theform
• Complete the payment flow and submit the form
• Check that the Thank You page shows the latest design
• The text should still be within the Summary table if the product name is very long
• Upon clicking the Save proof of payment button, the invoice PDF should be downloaded

Non-Payments Form

In Edit Mode

• Remove the payment variable/ component of the form
• Check that the Thank You page should reflect the default non-payment Thank you page
• Upon clicking the Save proof of payment button, the page should be refreshed/ reloaded

In Preview Mode

• Click on the Preview (eye) button of the form in admin mode
• Check that the Thank You page shows the default, non-payment design
• Upon clicking the Save proof of payment button, the page should be refreshed/ reloaded

In Actual Form

• Click on the share button to launch the form
• Check that the Thank You page shows the default, non-payment design
• Upon clicking the Submit another response button, the form should be refreshed to show a new form

Deploy notes

• 20240214_mrf-workflow-field-locking : This DB migration script adds the edit key for all workflow steps, which allows users to choose the fields each respondent is allowed to edit. To preserve existing behavior, all respondents must be allowed to edit all fields. Therefore, a copy of the form fields (excl non-input fields section, statement and image) are copied into every edit key.
• mrf-retain-workflow-in-submissions : This DB migration script creates a new workflow key in all existing mrf submissions, populated with the form's existing workflow. From this point on, workflows should be captured when the submission is initially created (i.e. the workflow is started)

[KenLSM]

Ensure that design is updated in Preview mode
The text should still be within the Summary table if the product name is very long

@kathleenkhy Non-blocking issue

Text bleeds through on preview mode (doesn't bleed on edit nor actual form)

[KenLSM]

1 non-blocking issue. LGTM