Feature/digital world clock

[miguelsg29]

This PR introduces a new built-in Digital World Clock widget alongside the existing analog world clock:

• Displays digital time for configured world clock time zones.
• Automatically respects ImmortalSettings.use24HourClock (12-hour vs 24-hour format).
• Responsive design: dynamically adjusts font size and alignment for 1, 2, 3, or 4 active time zones.
• Includes Spanish translations in I18n.kt.

[starbrightlab]

Nice addition — reviewed the two world-clock commits (independent of the i18n base). Correctness is solid: DST-safe (TimeZone.getTimeZone(zone)), respects use24HourClock (AUTO/12/24), and the LaunchedEffect tick actually updates. Integration follows the existing analog-widget pattern at all the right points, DisposableEffect cleans up the observer, no new persisted setting → tripwires stay green. This is close to mergeable.

A few nits before merge:

1. Don't repurpose the Timers glyph. ca7cab9 changed the shipped Timers icon ⏱ → ⌛ purely to free ⏱ for the new clock (HomeActivity.kt:3198). That silently alters an existing widget (and an hourglass suits a timer worse). Please give the digital clock its own glyph and leave Timers as-is.
2. Tick per-minute, not per-second. The digital face shows only HH:mm yet wakes every second (delay(1000)), and remember(zone, now, ...) re-keys on now so it memoizes nothing. On an always-on OLED launcher, per-minute is easier on power/burn-in.
3. Optional: the digital and analog widgets share ~all their scaffolding (state, lifecycle observer, tick, responsive layout) — a shared helper would avoid future double-maintenance. And at 3–4 zones the time Text is maxLines=1 with no overflow = Ellipsis, so a wide "12:45 PM" can clip.

Fix 1 and 2 and I'm happy to merge.

[starbrightlab]

Reviewed the Digital World Clock and I like it. The minute-boundary tick is genuinely nicer than the analog widget's 1-second poll, the responsive sizing for 1-4 zones is well thought out, and making the analog clock responsive along the way is a welcome touch. I want this in.

Two things block merging as filed:

1. The branch is a stack. It carries the Google Photos fix (already shipped in 1.65 via Fix Google Photos pagination & high-res portraits (closes #155) #168) and the full Spanish i18n sweep (the subject of Fix Google Photos pagination (#155) & Add Spanish translation (i18n) #164) underneath the three widget commits, so it conflicts with main and can't be reviewed or merged independently. Same ask as on Fix Google Photos pagination (#155) & Add Spanish translation (i18n) #164: once that PR is settled, rebase this onto main so it's just the widget commits (ca7cab9, 1827d67, 797e7da). The widget title currently calls I18n.translate(...) and reads the language setting, so if the i18n layer changes shape in review, those two hooks are the only places this PR needs to follow.

2. Time format: main recently moved date/time formatting to DateFormat.getBestDateTimePattern (Refactor date formatting to fully support global locales natively #156) so patterns adapt to the user's locale. Please use that here instead of the hardcoded "HH:mm" / "h:mm a" (skeletons Hm and hm).

If the rebase is a pain, happy to cherry-pick the three widget commits myself with authorship preserved, same as #168. Thanks again, this and the transitions PR are shaping up to be a great run of contributions.