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/THEME.md

@@ -63,10 +63,10 @@ you set), and a palette pass that overwrote a colour the sun path had chosen its
 1. **A role**: one line in `enum Role` and one row in `ROLES`, in the same order (the tests read
    both). The light value is the design; choose the dark value on a render, not in the table.
 2. **In firmware code**: `theme::color(theme::YOUR_ROLE)`. Never `lv_color_hex(0x...)`.
-3. **In a board profile**: the widget takes a paint. For a new combination add it to `enum class
-   Paint` and `PAINTS`, a colourless `- id: paint_<name>` in the `style_definitions` of both profiles,
-   and `theme::fill(id(paint_<name>), Paint::<name>);` in their `theme::paints` list. Then
-   `python3 tools/generate_packages.py`.
+3. **In the profiles**: the widget takes a paint. For a new combination add it to `enum class
+   Paint` and `PAINTS`, a colourless `- id: paint_<name>` in the `style_definitions` of `packages/core.yaml`
+   (or of one board file, for a paint only that board uses), and `theme::fill(id(paint_<name>), Paint::<name>);`
+   in the core's `theme::paints` list (a board-only paint goes into the board's `BOARD_PAINT_FILL` hook).
 4. **Something drawn once and kept that changes colour by state**: set it where the state is drawn,
    and make sure the redraw above reaches that code.
 5. A local colour always wins over a paint: an object that takes a paint must not also get a local