Keep the token, verifier and compliance instances alive #268

Description

The vault and the oracle extend their contract instance through crates/storage. The share token, the identity verifier and the compliance stub never do: OpenZeppelin extends their balances, roles and modules, but leaves the instance to the implementer. When an instance's TTL runs out it is archived, and every call to that contract fails until someone restores it. On testnet the token, verifier, compliance and asset instances already read liveUntilLedgerSeq = 0.

Steps to reproduce

1. Deploy the set and leave it idle past the instance's initial TTL.
2. Call claim_deposit or transfer.
3. The share token's instance is archived, so the call fails.

Expected vs actual behavior

Expected: every call that does work on the token, verifier or compliance contract extends its instance to 30 days, as the vault does.
Actual: only reads and writes of persistent entries are extended; the instance decays.

Additional context

The ops runbook and the TTL policy follow in a separate issue.