[Task]:Change queue Cinder feature testing

[ioanarusiczki]

Description

Try all scenarios from #15344 with Change queue instead of Escalate to AMO

Acceptance Criteria

In order to close can be closed since the Escalation bewteen queues has been working

Unsure about the Change queue feature - should be checked too

Checks

• If I have identified that the work is specific to a repository, I have removed "repository:addons-server" or "repository:addons-frontend"

┆Issue is synchronized with this Jira Task

[ioanarusiczki]

@eviljeff

I tried with Change queue scenarios from #15344 and worked with one exception (the second point I described below)

There would be 2 things:

• for all case, when the reporter/developer appeals land in Legal with "Change Queue" there is no "Uphold decision" or "Adjust decision" so I chose a policy that would disable or Ignore (instead of Approve).

• Ignore policy works instead of Approve for a developer appeal (Legal queue does not have Approve in the list of actions)-> content is reinstated but when used to resolve a reporter appeal it would not send the final email that the previous decision was correct. When I "escalated" the reporter appeal I had "Uphold decision" for this which worked just fine.

[eviljeff]

@ioanarusiczki this is a bug in Cinder, looks like - (imo) changing queue shouldn't break the special appeal functionality. Can you log a bug in lindie?

[ioanarusiczki]

Ok, done