Skip BBMs referencing dropped tables in single-record bug retry

Max Oreficerequested to merge
morefice/skip-dropped-table-bbm into master

Ref: #595138 (closed)

What does this MR do and why?

Mark BackfillSlackIntegrationsScopesShardingKey as finalized in the execute migration (20260302103001) that retries BBMs affected by the single-record bug (!224446 (merged)).

This BBM writes to slack_integrations_scopes_archived, a table that was dropped in 20260225213309.

Re-executing it is impossible as the table no longer exists, causing a PG::UndefinedTable error. Instead of skipping, we mark it as finalized (the terminal state) so it doesn't remain in paused state.

We will also need to backport this to %18.10.

Edited by Max Orefice

Merge request reports