Corregido To-dos

Fixed repeating To-dos drifting off the 31st, and reminders sent twice

A To-do that repeats every month from the 31st now falls on the last day of shorter months and comes back to the 31st, and a yearly one on 29 February returns to it in leap years. To-do and text reminders go out once, even when sending fails half way, and someone who is in a document, a design, a chat, Helpdesk or Walkie Talkie no longer drops out for a moment when one check-in is late.

Every-N-months and yearly repeats keep the series' first day (RecurrenceRule::nextOccurrence with the anchor), so 31 January no longer becomes 3 March, and a date clamped to a short month no longer becomes the series' day for good; monthly on a day later this month is no longer skipped. To-do reminders (TodoReminder::claimForSending) and booking text reminders (Booking::claimSmsReminder) are claimed with one UPDATE before they are sent; a text Twilio refused is given back for a later run. A daily or weekly scheduled job whose minute the coordinator missed starts at the next minute, once per due time (scheduled_jobs.lastDueAt, migration 10954). The website storage clean-up removes a blob only while it is unlisted and unused for an hour, checked in the statement that removes it, and under a per-website lock that uploads and builds hold from storing a file to listing it, so a file a new version takes again is never deleted. Presence rows count for 60 seconds (Presence::WINDOW_SECONDS) against heartbeats of at most 25 seconds, so one late or failed heartbeat no longer drops a person.