Drive the holder lifecycle end to end on testnet

[luchobonatti]

User story / Problem statement

The interface lane exits when the full holder lifecycle runs against testnet through the real app. The Playwright harness exists but drives nothing, and a lifecycle that spans a notice period cannot be tested by clicking through it by hand every time.

Expected outcome

One end-to-end run covering the whole holder journey, on network, through the app.

Acceptance criteria

• a holder gets allowlisted, then requests a deposit and sees the escrow
• the treasury fulfills, driven from the treasury console
• the holder claims shares and the balance appears
• a redemption request moves the shares into the vault
• the treasury fulfills the redeem side, the holder claims the asset
• a cancellation path covered on both sides
• a de-listed holder is proven to still claim a fulfilled position
• the run is repeatable and does not depend on state left by a previous run

Technical notes

Notice periods make this slow by design. Deploy the testnet instance with a short notice_secs for the e2e, and cover the real notice separately.

The de-listed case is the one worth automating hardest: it is the promise ADR-0016 makes most loudly, and the one a refactor is most likely to break.

Depends on #15 for the deployment and #16 for the treasury side.