Add models to allow cinder decisions to exist without a cinder job or abuse report

[eviljeff]

part of https://mozilla-hub.atlassian.net/browse/AMO-116

Currently our models expect an abuse report to be filed against a target (either add-on, rating, collection, or user); that report to be submitted creating a job, and then a decision made on the job. But we also need to make decisions on content that didn't come from an abuse report, and without the abuse report we don't have a target, and without a report we don't have a job. We need to create new models and migrate some data from the old models.

┆Issue is synchronized with this Jira Task

[ioanarusiczki]

@eviljeff let me know if I should test anything for this.

[eviljeff]

@ioanarusiczki it's all model changes with (hopefully!) no observable difference at this point. You can verify everything has been migrated correctly to the new models by attempting to appeal a decision that was made before 2024-03-20

[ioanarusiczki]

I've sent an appeal https://addons.allizom.org/en-US/abuse/appeal/57130/59242fd9-37d8-422d-985a-c2af3597443c/ for a decision taken on 14th March

The appeal is in Stage Listings Queue:
https://stage.cinder.nonprod.webservices.mozgcp.net/job/3da34d0e-4c10-429f-bdf0-b586d8340043

Also , decision +appeal https://stage.cinder.nonprod.webservices.mozgcp.net/job/bb865b45-fc9b-4143-8435-d42afe748cc0 sent today looks good.

[KevinMind]

Old Jira Ticket: https://mozilla-hub.atlassian.net/browse/ADDSRV-753