Build every screen from one shared core plus a small file per board, the same firmware as before (0.2.84)

The two board profiles (5,000 lines each, 87 % the same text) become packages/core.yaml and one file per
board under packages/boards/: the hardware, a table of 84 sizes and font sizes, 18 hooks with the lines of C++
only that board adds inside a shared lambda, and the board's own sections. packages/cyd.yaml and
packages/guition.yaml keep their names and places (a screen installed from ESP Screens builds as before);
home-like-2432s028.yaml and guition-4848s040.yaml become the same entries for a checkout.

The firmware stays 0.2.70: the C++ ESPHome generates for each board, through the checkout profile and
through the GitHub package route, was compared line by line with the old profiles' (docs/TEST_RESULTS_0284.md).
tools/check_packages.py replaces tools/generate_packages.py; tools/profiles.py gives the tests and tools the
three files as one; docs/PROFILES.md says how the files fit together and how a board is added.

Co-Authored-By: Claude Fable 5.1 <noreply@anthropic.com>

docs/SETTINGS.md

@@ -141,7 +141,8 @@ The screen's preferences hold the value, so the entity reads it in a lambda inst
 (`restore_value` cannot be combined with a lambda). A switch publishes its own changes. A number, time or
 select takes `update_interval: never` and one line in `apply_screen_settings`, which publishes it when it
 differs; that script runs after every change and on every Home Assistant connection (the time sync), so the
-entity has a value before Home Assistant reads the states. Then run `python3 tools/generate_packages.py`.
+entity has a value before Home Assistant reads the states. The entities live in `packages/core.yaml`; the
+Rotation select, which only a Guition has, in its board file (docs/PROFILES.md).
 
 ### 4. The add-on