We will be repurposing the existing AbuseReport model to also track feedback and and content violation reports we will be handing to satisfy our DSA requirements.

Broadly we need to:

• add decision category (disable/ban/etc)
• probably* add the policy name and/or uuid the decision was made under
• add reporter email and name (the user may be authenticated also)
• change categories ... (personally) I lean towards entirely new categories and then we can translate the old categories in the serializer where appropriate while we're still getting the old reports
• appeal state is tricky - I suppose if we're limited to just one appeal each per reporter and target then a flag on the model is sufficient. Otherwise we'd need an intermediate model.

*there is a bunch of extra metadata sent with the webhook response, but unless we need it I guess we don't need to store it in the AMO DB.

┆Issue is synchronized with this Jira Task