FORMS-1155 lock down form version viewing

[BrandonSharratt]

Description

Lock the viewing / exporting of versions if you know the form guid and can submit it.
Because other things rely on the existing functionality it will only strip form versions from the api response, and only if the user is passed in and doesn't have requisite permissions

Frontend changes will show an error if the api doesn't return versions in the response

Type of Change

fix (a bug fix)

This is a breaking change because ...
Somethings may be relying on getting the value when it shouldn't be returned and the api will no longer return it

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

[nimya-aot]

@BrandonSharratt Could you please deploy this PR to the PR environment so the Cypress tests can run and we can confirm that nothing is broken?

[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 251d559 deployed at https://chefs-dev.apps.silver.devops.gov.bc.ca/pr-1777

[BrandonSharratt]

@BrandonSharratt Could you please deploy this PR to the PR environment so the Cypress tests can run and we can confirm that nothing is broken?

Deployed now @nimya-aot

[nimya-aot]

@BrandonSharratt Could you please deploy this PR to the PR environment so the Cypress tests can run and we can confirm that nothing is broken?

Deployed now @nimya-aot

thanks!

[jasonchung1871]

If this fails, a more appropriate message should be considered. It could be an error message specifically for getFormPermissionsForUser failing.