Put ESP Screens in English and keep layouts when entity IDs change (0.2.40)

Everything a user sees or reads is now English: both boards' labels,
status replies and logs, the ESP Screens editor and Alerts cheatsheet,
and the README and guides (docs/TILES.md, CALIBRATING.md, ACCEPTANCE.md
and TROUBLESHOOTING.md replace the Dutch file names). Labels follow
Home Assistant's own English names (Heat/Cool modes, Heating/Cooling
actions, Away, Returning to dock, weather conditions), dates use English
abbreviations and the top bar writes numbers the English way. Docs use
HA 2026.9's menu names (Settings -> Apps, App store, Settings -> Tools).
Unused legacy files (home-like.yaml, buttons.yaml, a.out) are removed.

Firmware 0.2.34 names its entities in English. Home Assistant registers
a renamed ESPHome entity under a new entity ID, so the inbox
text.<screen>_tegelinstellingen becomes text.<screen>_tile_settings and
the layout stored under the old ID would be lost. The manager now
recognises the screen by its device, during a run or after a restart,
and moves its layout and update history along; the Update button and
the nightly round follow the screen through the rename. Screens that
still run 0.2.33 or older keep working: both languages are matched.

Main is the only release branch from now on.

Tested on a Home Assistant Yellow (HA 2026.9.1) with both bench boards:
see docs/TEST_RESULTS_0240.md.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

tests/test_cyd_ui.cpp

@@ -61,21 +61,21 @@ int main() {
   wide.update(275, 200, 3); wide.update(300, 200, 3); wide.update(340, 200, 3);     // a real swipe: the reference
   wide.update(380, 200, 3);                                                        // settles, the finger keeps going
   assert(!wide.accept(1100, 1));
-  assert(wide.reason().rfind("verplaatst", 0) == 0);
+  assert(wide.reason().rfind("moved", 0) == 0);
   wide.begin(2000, 200, 200, 3);
   wide.update(400, 400, 5);                                                        // a second finger elsewhere
   assert(wide.accept(2050, 1)); // ignored: only contact 3 is followed; 50 ms is long enough here
   wide.begin(3000, 200, 200, 3);
   assert(!wide.accept(3010, 2)); // 10 ms is below the capacitive minimum
-  assert(wide.reason().rfind("te kort", 0) == 0);
+  assert(wide.reason().rfind("too short", 0) == 0);
   wide.begin(3100, 200, 200, 3);
   assert(wide.accept(3160, 2));
   assert(wide.reason().empty());
   assert(!wide.accept(3170, 2));
-  assert(wide.reason() == "al verwerkt in dit contact");
+  assert(wide.reason() == "already handled in this contact");
   wide.begin(3200, 200, 200, 3);
   assert(!wide.accept(3260, 2)); // same tile within 600 ms
-  assert(wide.reason() == "dezelfde knop binnen de dendertijd");
+  assert(wide.reason() == "same button within the debounce window");
   // No movement limit (0): a capacitive board leaves the drift decision to LVGL's press-lost.
   cyd::TouchGuard free;
   free.configure(0, 20);