[Task]: implement adding and removing a block for versions of an add-on in the reviewer tools

[eviljeff]

Description

part of https://mozilla-hub.atlassian.net/browse/AMO2-689

Adding a block for one or more versions of a single add-on, and removing a block for one or more versions of a single add-on:

Acceptance Criteria

• Adding a block: Select one or more versions of a single add-on, providing an option to force-disable the add-on, and a textbox to enter a block reason.
  • Milestone n+1: Proper block reasons like reject reasons. Tbd with Legal, need to consider source of thruth, given that canned responses for reject reasons are to be replaced
  • Need to align with Legal which emails are sent (especially if the add-on is force-disabled as part of the block), as well as the copy
• Removing a block: Select one or more versions of a single add-on, providing an option to force-enable the add-on.

Questions

• How do we re-enable the add-on and potentially the versions? What message do we send out to the developer when a version is unblocked?
• If this is used as a workaround to edit a block, how does that affect sending emails? I.e. We’d send an unblock email and a block email right after.

Checks

• If the issue is ready to work on, I have removed the "needs:info" label.

┆Issue is synchronized with this Jira Task