feat: send email for export raw

[pyphilia]

For exporting, the zip creation is handled in the background and a download mail is sent. Meanwhile the request responds with 202 accepted.

The export request is logged in a corresponding table. Currently it does not do anything.

Expiration date is 7 days. Nothing cleans up after 7 days.

!! guests cannot use export. So we should use /download for downloading.

Following this PR we will:

• add a queue, for the zip generation to be handled on a worker
• this queue will also receive a schedule job to delete all archives and logs corresponding to old requests.

I didn't reuse action_request_export as we might want different schemas for actions export (json, csv) and item themselves (raw, graasp). We might want different expiration time, also we might want export not related to items (eg. export member data).

TODO

• write tests

[spaenleh]

Thank you for this PR.

I have left comments related to general naming, we can decide to change them or not. I see quite a lot of the names would need to be changed.

Some of the comments are a bit nitpicking. Let me know.

[pyphilia]

Here are the links within the emails, should add ellipsis on the link maybe?

[spaenleh]

@pyphilia I think adding an ellipsis defies the purpose of putting the link in plain text. users should be able to copy the link if needed even if it is not recognized by the email client. What does the plain text variant look like ?

[pyphilia]

Well people can hover the link, or right click and copy. If we wanted to lure users, we could change the text and have a different url in the href.

[spaenleh]

Great work !

[sonarqubecloud]

Quality Gate passed

Issues
3 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud