Description

We currently run some checks depending on usage that lead to automatically flag the add-on for review when abuse_reports_ratio_threshold_before_flagging on the corresponding UsageTier is met. Let's add:

• ratings_ratio_threshold_before_flagging (same idea, but using number of ratings)
• abuse_reports_ratio_threshold_before_blocking (disables and block the add-on instead of just flagging)
• ratings_ratio_threshold_before_blocking (same)

We also need to adjust the tasks/create new ones (triggered from update_addon_average_daily_users() like the existing ones) to run those checks every day like the existing ones.

"Disable and block" needs to force-disable the add-on and soft-block all its versions. 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 developer(s)
• Be gated by 2nd level approval condition

Acceptance Criteria

• abuse_reports_ratio_threshold_before_blocking
• ratings_ratio_threshold_before_flagging
• ratings_ratio_threshold_before_blocking

┆Issue is synchronized with this Jira Task