Port blocked-peer cleanup rule and cleanup-failure journey actions from iOS #1143 #1797

Android #1693 is the twin of synonymdev/bitkit-ios#1143, and two parts of the iOS change are missing from it.

1. Profile-removal cleanup does not exclude blocked peers

• On iOS, On-chain send reports success before broadcast is attempted; failed broadcast leaves inputs marked spent #1143 leaves blocked peers out of the private-list cleanup during profile removal.
• On Android, PrivatePaykitRepo.clearPrivatePaymentLists builds cleanupKeys from linkedPublicKeys and hasPublishedPrivatePaymentList, with no check for BLOCKED (PrivatePaykitRepo.kt:2257-2259 at c228adb7b).

The iOS exclusion is the source of an open MEDIUM on #1143 (review):

• Profile removal never withdraws the list it shared with a blocked peer.
• The Paykit SDK then refuses to downgrade private_payments (require_app_capability_downgrade_safe).
• Profile deletion stops at "Finish local cleanup". This was reproduced after a withdrawal failed during contact deletion.

Settle the Android behaviour once that thread is resolved. Either:

• port the final iOS rule, or
• record the platform difference in the journey <description> and journeys/README.md.

Until then, the two apps disagree on blocked peers.

2. Journey actions not ported

• journeys/profile/profile-cleanup-failure.xml has 12 actions on Android at c228adb7b and 16 on iOS at 065a4c6f2.
• Port actions 13-16 (the withdrawal failure on contact deletion, and profile deletion afterwards), keeping the same prose, per the journey porting rule in CLAUDE.md.

Status

Neither point has been run on Android. Both come from reading the code at c228adb7b.

Related: #1693, synonymdev/bitkit-ios#1143.