Store encrypted profile information with no way to access it without the key which is sent to client and never stored on the server

[deepakprabhakara]

generate a per code/token encryption key and send it to the client, store the encrypted value so that PII exposure of storing profile is dropped to zero

What does this PR do?

Fixes # (issue)

Type of change

• Updated dependencies
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• This change requires a documentation update

How should this be tested?

• Existing unit tests

Checklist:

• My code follows the style guidelines of this project
• I have performed a self-review of my own code and corrected any misspellings
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[alnr]

Looks good! Crypto implementation is OK as far as I can see.