[Bug]: promoted add-ons and resolving them with override decisions - override approve with disable

[ioanarusiczki]

What happened?

While making some regression testing (after #15306)

The 2nd level approval + override scenarios

Case is: override approve with disable

1. A report for a promoted add-on goes to Cinder and decision is Approve (an email goes to the reporter as expected, with an appeal url attached) ✅
2. It's overridden with a policy that would disable: this action is held for a decision in 2nd level approval queue from rev tools ✅
   https://reviewers.addons-dev.allizom.org/en-US/reviewers/decision-review/6627
3. Observe there are 2 options available: proceed and approve (without forward to rev tools, the third option is usually present with abuse reports) ❓
4. Decision in rev tools is: approve

What did you expect to happen?

A new email is sent to reporter but I think it's not correct (it should say to reporter that the final decision is that content stays up without an appeal url attached)

Instead of approve , choosing proceed at step 4 -> looks good

Is there an existing issue for this?

• I have searched the existing issues

┆Issue is synchronized with this Jira Task

[ioanarusiczki]

Similar issues

#15329
#15330