Description

A new scanner action should be available that automatically force-disable the add-on and soft-block all its versions.

Same behavior as #15764 applies, it needs to work like a reviewer action would, and in particular:

• Record the decision with the "Deceive, mislead, defraud, phish, or commit or attempt to commit identity theft" policy/reason attached.
• Notify developers
• Be gated by 2nd level approval

On top of this, it should only work if the add-on average_daily_users is below a configurable value. Maybe we could have a boolean to enable/disable it on UsageTier, and check that the add-on is part of a tier with that boolean enabled.

Acceptance Criteria

• New scanner action is available that force-disables and soft-blocks the entire add-on

┆Issue is synchronized with this Jira Task