flag correct versions for a developer appeal

[eviljeff]

Fixes: mozilla/addons#15182 and fixes mozilla/addons#15247

Description

Flag the versions that were affected by a version rejection if the developer appeals.

Context

Until recently there was no easy way to reference the versions rejected by the ContentDecision, so we could only flag the current version if the developer appealed the rejection.

Testing

• enable all the DSA related waffle switches and have a Cinder API key in your settings
• Reject a version of an add-on in the reviewer tools - either an unlisted version or a non-latest version - i.e. a version that wouldn't be the addon's current_version (unlisted is better, because that's the use-case the issue was filed for)
• appeal that decision with the appeal link in the email
• go back to the reviewer tools and see that the appealed version is flagged for NHR

Checklist

• Add #ISSUENUM at the top of your PR to an existing open issue in the mozilla/addons repository.
• Successfully verified the change locally.
• The change is covered by automated tests, or otherwise indicated why doing so is unnecessary/impossible.
• Add before and after screenshots (Only for changes that impact the UI).
• Add or update relevant docs reflecting the changes made.

[KevinMind]

A few questions. Will try to verify.

[KevinMind]

The code and tests look good. I wasn't able to verify locally but that seems to be an unrelated issue. Happy to let further verification happen on dev.

[sentry-io]

Suspect Issues

This pull request was deployed and Sentry observed the following issues:

• ‼️ ConnectionError: b'{"detail": ["Appealer has already appealed this series of decisions"]}' olympia.abuse.tasks.appeal_to_cinder View Issue

_{Did you find this useful? React with a 👍 or 👎}