feat(explorer): refresh console data after on-chain mutations

Parent tracker: #436
Owning PR: #424
Depends on: #439 / PR #423

## Goal

Refresh active console data after confirmed on-chain mutations and completed card-funding landings.

## Scope

- Refetch active account queries after a receipt, then again after bounded 10-second and 30-second delays.
- Match checksummed and lowercase account variants.
- Exclude quote-only data from mutation refreshes.
- Coalesce the bounded delayed refresh schedule.

## Non-goals

- Refreshing on transaction submission before confirmation.
- Adding unbounded polling.
- Restacking, merging, or otherwise changing PR state.

## Acceptance criteria

- Submission alone does not refresh confirmed account state.
- A confirmed receipt refreshes active matching account queries.
- Checksummed and lowercase forms resolve to the same account.
- Delayed refreshes remain bounded and do not duplicate unnecessarily.
- Focused tests cover receipt timing, address variants, quote exclusion, and cleanup.

## Performance

Performance is relevant because this adds delayed refetches. Only active observers may be refreshed, and the timers must remain bounded and coalesced.

## Delivery

PR #424 remains based on PR #423 while the stack is open. After its predecessor merges, retarget it to staging and revalidate the exact head.

Start with PR #424 and its predecessor PR #423, then trace the explorer's active account queries and receipt handling. Use the acceptance criteria to verify refresh timing, address matching, quote exclusion, bounded coalesced delays, and cleanup; focused tests should cover those cases.

Written by the indexing model from the issue text.