FIO-7302: Prevent clearing the fields that does not exist on the current form revision if they were on the older one

[alexandraRamanenka]

Link to Jira Ticket

https://formio.atlassian.net/browse/FIO-7302

Description

What changed?

If there were some fields on the older form revisions that are not on the current one, and the user edits the submission done with an older revision, those fields are getting cleared during the validation (they are simply not set to the form data because there are no components with correspondent API keys).
With this fix after the validation is complete and right before replacing body's data with data that come from the validation, it will check if the form has revisions allowed and if there are some values paths in the original submission data (taken from the DB, not in the one that was sent fromt he client, so teh user won't be able to change those old fields values) and there are no correspondent components in the current form revision, and it will add those old fields values to the date that came from the validation.

Dependencies

https://github.com/formio/formio-server/pull/1397

How has this PR been tested?

I wrote an automates test, but this will be moved to the formio-server cuase it needs revisions allowed in order to work

Checklist:

• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation (if applicable)
• My changes generate no new warnings
• My changes include tests that prove my fix is effective (or that my feature works as intended)
• New and existing unit/integration tests pass locally with my changes
• Any dependent changes have corresponding PRs that are listed above

[brendanbond]

Since form revisions exist solely in the Enterprise Server, is there a case here for creating a hook here rather than hardcoding this into OSS formio?
e.g.

hook.alter('rehydrateSubmissionRevisions`, submission, (err, submission) => {...});

If you disagree I'm OK with this, it just seems to me a better idea to put enterprise server specific logic (in this case, form revisions) into the enterprise server codebase via hooks