[Bug]: Developer appeals forwarded to amo don't flag extensions/themes for HR

[ioanarusiczki]

What happened?

Followup for #15245

I tried the following scenario on dev and stage:

1. Sent reports to Cinder for extensions/themes
2. Chose a policy that would disable content
3. Sent the developer appeal
4. For extensions it goes in a different queue than the initial one T&S Escalations , theme appeals go back in AMO dev/stage themes queues
5. Forwarded developer appeals to AMO

on dev

https://reviewers.addons-dev.allizom.org/en-US/reviewers/review/634956
https://reviewers.addons-dev.allizom.org/en-US/reviewers/review/634957

on stage https://reviewers.addons.allizom.org/en-US/reviewers/review/2244256

What did you expect to happen?

forwarded developer appeals should flag versions for HR

This is not reproducible with reporter appeals forwarded to AMO rev tools
an example on dev https://reviewers.addons-dev.allizom.org/en-US/reviewers/review/634977
an example on stage https://reviewers.addons.allizom.org/en-US/reviewers/review/2244255

Is there an existing issue for this?

• I have searched the existing issues

┆Issue is synchronized with this Jira Task

[eviljeff]

I think this is the same underlying cause as #15247, so should be fixed with the same PR (not duping the issue though, so it can be validated separately when closed)

[ioanarusiczki]

I don't see this being reproducible on AMO dev.

Verified with:
an extension, developer appeal is escalated to Manual Review queue ✅ https://reviewers.addons-dev.allizom.org/en-US/reviewers/review-listed/635301
a theme, developer's appeal is escalated to Themes queue ✅ https://reviewers.addons-dev.allizom.org/en-US/reviewers/review/635305

and a reporter appeal escalated to manual review queue ✅ https://reviewers.addons-dev.allizom.org/en-US/reviewers/review-listed/635303