[Task]: handle abuse reports being directly associated with an appeal cinder job

[eviljeff]

Description

Cinder combines multiple abuse reports into a single job - i.e. if a job is already open for an entity (an addon, a rating, a collection, or a user) then rather than opening a new job, the report is attached to the existing job. We handle this fine. But we made an assumption that appeal jobs - where a previous decision was appealed by the reporter or the owner of the entity - were separate.

This assumption may not be correct. QA testing (#1728) has shown that reporting an entity that has an outstanding appeal job also combines that that report into the job.

Acceptance Criteria

• We need to make any necessary model changes to support the scenario of abuse reports being associated with an appeal job
• This also applies to appeal-appeal jobs (reporter-reports->decision:approve; reporter-appeals->decision:reject; owner-appeals)
• appeals on those decisions need to be tested (e.g. do we allow enough time?)

Checks

• If the issue is ready to work on, I have removed the "needs:info" label.

┆Issue is synchronized with this Jira Task