[tempus2016]

fix(cards): timed chores can't be started while the chore is locked

A timed chore only refused Start for a missing prerequisite, so one in its
recurrence cooldown, claimed first by a sibling, for a later part of the
day, past its window, not due today, at its weekly target or at a closed
set time could still be started — on classic and every designed style.

Start and Resume now take their locks from _choreLocks, the same helper
the classic row uses, and look disabled. Pause and Done stay live so a
session already running can always be ended. The wiki no longer lists
timed-task cards as ignoring first_come_claimed_mode.

fix(cards): a locked timed chore is dimmed and says why

Greying Start alone left a locked timed chore looking live, with no reason
given, unlike the standard rows. It now dims the same way under the same
modes (recurrence, first-come and dependency locks only under "dim"), and
names the reason under the chore's name in the standard rows' words —
"Available at 17:00", "Time has passed for this chore", "Do Teeth first",
the recurrence, who claimed it, and so on — in every design. A session
already running or paused stays at full strength so it can be ended.

fix(cards): a locked timed chore's opening time follows HA's clock

"Available at 17:00" and a set time's opening time on a locked timed
chore now go through the shared clock helper when it is loaded, so a
12-hour HA profile reads "05:00 PM" (#771).

fix(cards): a locked timed chore's cooldown reason uses the translated cadence

When the card has the translated recurrence label (fix/recurrence-label-i18n),
the timed card's lock reason uses it too instead of the raw key (#771).

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).