[Bug]: developer appeals can be attached to actions that won't have a good result

[ioanarusiczki]

What happened?

While making checks on #15182 I've noticed the following:

Case A:

• listed/unlisted versions are reviewed. Decision is to block + disable automatically these versions
• developer is getting an email and sends an appeal
• on the review pages the appeal can also be attached to force enable action

Result: an email is sent that the version(s) are now available but the're not (there are other actions to take before making them available again)

Tested with:
unlisted https://reviewers.addons-dev.allizom.org/en-US/reviewers/review-unlisted/635449
listed https://reviewers.addons-dev.allizom.org/en-US/reviewers/review-listed/635458

Case B:

• listed/unlisted versions rejected
• developer is sending an appeal
• versions get flagged for HR
• appeal can be attached to force disable action

Result: a new email with an appeal url is sent to developer

What did you expect to happen?

Maybe it should not be possible to attach the appeal to these actions.

After blocking there's other steps to take for resolving the appeal to reinstate content or deny the appeal.

Is there an existing issue for this?

• I have searched the existing issues

┆Issue is synchronized with this Jira Task

[ioanarusiczki]

Case C:

https://reviewers.addons-dev.allizom.org/en-US/reviewers/review-listed/635368

• a version was reported for abuse report and delay rejected
• delay expires the final email is sent to the developer with an appeal url
• developer sends the appeal
• the version is flagged for HR
• check the appeal from dsa section + confirm approval

Result: an email is sent about content being reinstated which is not correct