[Bug]: non dsa add-ons forwarded to Legal Escalations in Cinder don't seem to work with policies that take content down

[ioanarusiczki]

What happened?

Followup for #15255 (comment)
And the note from #15259 (comment)

First scenario

1. An approved listed version is forwarded to Legal from review page with Request Review from Mozilla Legal
2. Cinder Legal Escalations queue creates a new job
3. Decision is taken AMO Disable Addon https://stage.cinder.nonprod.webservices.mozgcp.net/job/2853a9f6-3793-4980-a9a2-0e98c9989c43

Result:
content is not disabled on AMO

Escalate to AMO policy for such an add-on -> won't send back of flag for review the version in rev tools

Second scenario

1. An awaiting review version is forwarded from the Manual Review queue to Legal. This could be a promoted add-on with a new version, or the auto-approval is disabled (manually or automatically)
2. Request review from Mozilla Legal
3. From Cinder Legal Escalations try a policy which disables the add-on https://stage.cinder.nonprod.webservices.mozgcp.net/job/b2028e94-0c12-4792-9d47-6934eb27b5e4

Result:
add-on is not disabled, the awaiting review versions are still flagged for HR in rev tools.

What did you expect to happen?

Disable content.

Are these add-ons supposed to go in Cinder if there are no reports/appeals attached? Right now any add-on can forwarded to Legal queue in Cinder.

Is there an existing issue for this?

• I have searched the existing issues

┆Issue is synchronized with this Jira Task

[eviljeff]

@wagnerand would you expect the (promoted|auto-approval-disabled|etc) NHR for the review to be cleared in the reviewer tools if the add-on is forwarded on to legal? (I'm assuming so, but double checking)