[Task]: Implement ability to have follow-up blocks for negative enforcement actions

[diox]

Description

Implement new "follow-up" enforcement actions: “Delayed soft-block in X days”, “Delayed hard-block in Y days”, “Delayed hard-block in Z days”
Each correspond to a possible second and third action in Add-on Policies violations enforcement actions that can occur after a negative action taken for a policy violation.

X, Y and Z are hardcoded in constants for now according to what Operations need. The name of the action could be like amo-delayed-short-soft-block or amo-delayed-mid-hard-block and amo-delayed-long-hard-block for instance (or maybe amo-hard-block-in-short-delay, amo-hard-block-in-medium-delay etc) to allow us to tweak the constants independently.

Those blocks should use BlocklistSubmission with disable_addon=False as the add-on should already be disabled when they are executed. Similarly, whenever we execute such a Blocklistsubmission, relevant versions should have been rejected already, so possibly look into adding a safeguard to prevent us from calling disable_versions_for_block() when creating the block ?

Those actions should not happen on their own. Automatically unblocking of add-on/versions upon successful appeal will be handled in #16119

Acceptance Criteria

• item 1

┆Issue is synchronized with this Jira Task