Runs every installed extension's erase path for one player.

Core's caller holds the transaction; this walks the installed set inside it, calls erase_player/1 on each extension that exports one, and stops at the first failure. See asobi_extension:erase_player/1 for why erasure is atomic across extensions rather than best-effort, and why the alternative to this callback is a cascade in the migration rather than a key in owns/0.

A caller must assert the result, because a bare {error, _} returned from inside asobi_repo:transaction/1 still commits:

asobi_repo:transaction(fun() ->
    ok = asobi_extension_erase:run(PlayerId),
    {ok, _} = asobi_repo:delete_all(...),
    ...
end).

The badmatch is what rolls the transaction back; the line naming the extension is logged here, before the reason is flattened into a badmatch term.

An extension that raises is caught rather than allowed to propagate, so the failure is attributed to a name before it becomes the caller's problem. Nothing runs after a catch: the Postgres transaction is already aborted at that point, and the only correct next statement is the caller's rollback.