Feat/attachments extra attrs

[marrouchi]

Motivation

In this PR, we add extra attributes to the attachment schema in order to have more control over access:

• createdByRef : user / subscriber
• createdBy : id
• resourceRef : The context where the attachment is used.
• access : Either public or private (access is public : blocks, content, and is private for message and avatars)

To achieve this we need to:

• Centralize file upload and access using attachmentService.store() method.
• Refactor Attachment DTOs
• Add ability guard to check access to the attachement based on the context.
• Use public signed Urls to download attachments and preserve "url" for extenal links
• Add extra attributes to the Attachment schema : createdByRef, createdBy, resourceRef and access
• Add support for Stream when storing files and enforce security around multipart upload
• Refactor channels design to allow the subscriber and avatar to be linked to each others.
• Update migration 2.2.0 to include new attributes
• Update frontend to send the resourceRef on each upload.

Related PRs:

All channels extensions developed so far have been updated to accomodate the new changes:

• Messenger: feat: add attachment extra attrs hexabot-channel-messenger#12
• WhatsApp: feat: add attachment extra attrs hexabot-channel-whatsapp#9
• Discord: feat: add support for attachment extra attributes hexabot-channel-discord#6
• Slack: feat: add attachment extra ttrs hexabot-channel-slack#9

How to test

The features below should be working as usual and must check the new attributes in DB + file in root directory (attachments or avatars)

• Previous DB data should be upgraded
• Attachment / Carousel / List blocks
• User avatar update
• Triggering Attachment blocks from any channel should respond accordinly
• Sending an attachment via the chat
• Access the attachment from the inbox
• Fetching and storing the subscriber avatar
• Attempt to access an attachment without the right permission should fail.

Type of change:

Please delete options that are not relevant.

• 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

Checklist:

• I have performed a self-review of my own code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• I have added unit tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes

[yassinedorbozgithub]

I have faced an issue when trying to edit a content

[yassinedorbozgithub]

I have faced an issue with the migrations

Also, have the same issue by running this command from the container shell

npm run cli migration migrate up