FIO-7498 Changed the passing of a data field to decrypt hook

[antonSoftensity]

Link to Jira Ticket

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

Description

Changed the way to pass the data to decrypt hook, so that if decrypt fails it should display hashed value instead of buffer array

Dependencies

Use this section to list any dependent changes/PRs in other Form.io modules

How has this PR been tested?

Use this section to describe how you tested your changes; if you haven't included automated tests, justify your reasoning

Checklist:

• I have completed the above PR template
• 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]

I'm suspicious of this change only because other decrypt routines that we use contain a check for buffer-like properties before proceeding. Can you explain why this situation differs?

[antonSoftensity]

the way I see it is we have 2 ways to pass data to decrypt function, just the regular data object, or the buffer field inside of it (i.e. formio-server encryptDecrypt passes a data object to decrypt function). In this case, I made this particular change so that if the server can't decrypt data (in case we don't have a secret or the project isn't loaded), the returned data would be in form of hashed value instead of the buffer array