Pre-Publish Functionality / Salesforce Publish Integration

[ShadeWyrm]

Summary | Résumé

#2605
+
#3313

Test instructions | Instructions pour tester la modification

Create form. Go to settings page, set the new setting.

Unresolved questions / Out of scope | Questions non résolues ou hors sujet

-> Out of scope: Full [User] Lifecycle.
-> Department Identification

Pull Request Checklist

Please complete the following items in the checklist before you request a review:

• Have you completely tested the functionality of change introduced in this PR? Is the PR solving the problem it's meant to solve within the scope of the related issue?
• The PR does not introduce any new issues such as failed tests, console warnings or new bugs.
• If this PR adds a package have you ensured its licensed correctly and does not add additional security issues?
• Is the code clean, readable and maintainable? Is it easy to understand and comprehend.
• Does your code have adequate comprehensible comments? Do new functions have docstrings?
• Have you modified the change log and updated any relevant documentation?
• Is there adequate test coverage? Both unit tests and end-to-end tests where applicable?
• If your PR is touching any UI is it accessible? Have you tested it with a screen reader? Have you tested it with automated testing tools such as axe?

[timarney]

Couple of linting errors if you missed them :)

5ed3d9a#file-app-gcforms-locale-form-administration-form-builder-id-settings-components-responsedelivery-tsx-L145

[timarney]

Noting given the migration this won't be testable with the review environments given we use staging resources (which is fine just flagging).