[tempus2016]

fix(timed): a timer reaching its cap no longer breaks the refresh, and a locked one isn't paid out unchecked

The cap auto-stop runs inside the coordinator's own refresh, and stopping
the session asked for another refresh from in there. Home Assistant's
refresh debouncer isn't re-entrant, so the update failed with "Debouncer
lock is not re-entrant". The stop now takes refresh=False from inside the
update (the running update returns the fresh state), and the stale-session
sweep can skip its refresh the same way.

A running timer whose chore the child can't do any more (a prerequisite
added after it started, a cooldown, a rota or vacation change) still paid
out when it stopped. The completion path would refuse that chore, so the
stopped time now goes to a parent to approve instead of being paid
automatically; the child's time is kept. Pause and Done stay live on the
card so a running session can always be ended.

Testing

• Unit and frontend tests for this change are included in the diff; the whole batch passes the full suite.
• Checked on the dev Home Assistant instance as part of the v7.7.1 pre-release gate (desktop and 360/375/393/768 phone/tablet widths).