WIP: encrypt issue and note table

What does this MR do?

This MR encrypts Issue table and Note table at rest using Openssl encryption mechanism. Issue/note create/update is encrypted before writing data to Postgres. I understand this decryption approach might cause risks, as it requires every issue reference needs to be encrypted/decrypted. I'm open for advice on how to best implement this at app level.

Screenshots

Does this MR meet the acceptance criteria?

Conformity

• Changelog entry
• Documentation (if required)
• Code review guidelines
• Merge request performance guidelines
• Style guides
• Database guides
• Separation of EE specific content

Availability and Testing

• Review and add/update tests for this feature/bug. Consider all test levels. See the Test Planning Process.
• Tested in all supported browsers
• Informed Infrastructure department of a default or new setting change, if applicable per definition of done

Security

If this MR contains changes to processing or storing of credentials or tokens, authorization and authentication methods and other items described in the security review guidelines:

• Label as security and @ mention @gitlab-com/gl-security/appsec
• The MR includes necessary changes to maintain consistency between UI, API, email, or other methods
• Security reports checked/validated by a reviewer from the AppSec team