feat: CCP-4720: Implement public form submission privacy

[gary-jipp]

Description

Type of Change

feat (a new feature)

Checklist

• I have read the CONTRIBUTING doc
• I have checked that unit tests pass locally with my changes
• I have run the npm script lint on the frontend and backend
• I have added tests that prove my fix is effective or that my feature works
• I have added necessary documentation (if appropriate)
• I have approval from the product owner for the contribution in this pull request

Further comments

Enable Public Form Submission privacy. Success page only shows for submitter. Anyone else with the URL will only see a generic success page

[github-actions]

Coverage Report (Application)

Totals
Statements:	78.38% ( 9999 / 12757 )
Methods:	77.09% ( 1053 / 1366 )
Lines:	81.14% ( 6128 / 7552 )
Branches:	73.4% ( 2818 / 3839 )

[github-actions]

Coverage Report (Frontend)

Totals
Statements:	69.45% ( 10745 / 15471 )
Methods:	62.94% ( 1882 / 2990 )
Lines:	74.65% ( 5964 / 7989 )
Branches:	64.54% ( 2899 / 4492 )

[bhuvan-aot]

@gary-jipp I see the tooltip has good amount of information.
When unchecked, the submitter can still view and print their submission while the success page stays open, but anyone else opening the URL sees only the confirmation message. The email-receipt option is turned off because forwarding the receipt would defeat this protection. You may want to adjust your post-confirmation message to include any details the submitter might need later.

I am not sure if post-confirmation message can be modified by form designer/owner.

[nimya-aot]

When an authenticated IDIR user(not a reviewer or anyone in team members) attempts to open a public form submission using the submission URL (a rare scenario), with Hide submission contents enabled and **not allowing submitters to email themselves a copy of their submission, the page throws an error. I think we need to handle this scenario rather than throwing error

[usingtechnology]

When an authenticated IDIR user(not a reviewer or anyone in team members) attempts to open a public form submission using the submission URL (a rare scenario), with Hide submission contents enabled and **not allowing submitters to email themselves a copy of their submission, the page throws an error. I think we need to handle this scenario rather than throwing error

I agree, that is a terrible user experience...

[nimya-aot]

working good

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[github-actions]

Release e09c80d deployed at https://chefs-dev.apps.silver.devops.gov.bc.ca/pr-1892