Harvest enum values from controllable definitions and fixtures, fix generation docs (#2085)

## Summary

While reviewing the enum-generation documentation, I found the generator
was leaving real data on the table and the docs describing it were
partly wrong. This PR fixes both.

### 1. Harvest `OverkizCommandParam` from controllable definitions
`extract_state_values_from_servers` only read `OverkizCommandParam`
values from `protocols.*.states[].enumValues`, missing:
- ~1600 `DiscreteState` `values` arrays in `controllableDefinitions`
- `enumValues` on command parameters in the protocols section

This adds **313 previously-missing parameter values** (e.g. `A_B_C`,
`AUTO_FAN`, `MAINS_SINGLE_PHASE`).

Two safety details:
- Purely numeric values (`"1"`–`"9"`) can't be valid Python identifiers
— now skipped and reported in the run output instead of emitting broken
code.
- Two verbatim API values contain Cyrillic characters (`pусский`,
`yкраїнськийon` from the Atlantic server) — `RUF001` added to the
generated file's `noqa` header.

### 2. Merge UI enum values from setup fixtures
`state.py` and `command.py` already merged
`tests/fixtures/setup/*.json`, but `ui.py` and `ui_profile.py` did not.
They now do, capturing real devices whose UI values the reference
endpoints of our available servers don't expose. Adds the `Startable`
and `StatefulStartable` profiles and lets three previously hardcoded
widgets come from real data.

`protocol.py` stays metadata-only — Protocol members need the full
`id`/`prefix`/`name`/`label`, which fixtures don't carry.

### 3. Fix `docs/development-utils.md`
The `generate_enums.py` "Generates" table omitted `state.py` entirely,
listed an incomplete source for `command.py`, and didn't reflect
fixtures as a source for the UI enums. Corrected and expanded.

## Test plan
- [x] `uv run utils/generate_enums.py` regenerates cleanly
- [x] `ruff`, `mypy`, `ty` pass
- [x] 456 tests pass

Author: iMicknl

docs/development-utils.md

@@ -65,12 +65,17 @@ uv run utils/generate_enums.py
 | File | Source |
 |------|--------|
 | `pyoverkiz/enums/protocol.py` | `referenceMetadata.protocolTypes` |
-| `pyoverkiz/enums/ui.py` | `referenceMetadata.uiClasses`, `uiWidgets`, `uiClassifiers` |
-| `pyoverkiz/enums/ui_profile.py` | `referenceMetadata.uiProfiles` |
-| `pyoverkiz/enums/command.py` | `protocols.*.commands` + `tests/fixtures/setup/*.json` |
-| `docs/ui-profiles.md` | `referenceMetadata.uiProfiles` |
+| `pyoverkiz/enums/ui.py` | `referenceMetadata.uiClasses`/`uiWidgets`/`uiClassifiers` + `tests/fixtures/setup/*.json` |
+| `pyoverkiz/enums/ui_profile.py` | `referenceMetadata.uiProfiles` + `tests/fixtures/setup/*.json` |
+| `pyoverkiz/enums/state.py` | `protocols.*.states`, `controllableDefinitions.*.states`/`attributes` + `tests/fixtures/setup/*.json` |
+| `pyoverkiz/enums/command.py` | `protocols.*.commands`/`states`, `controllableDefinitions.*.states` + `tests/fixtures/setup/*.json` |
+| `docs/ui-profiles.md` | `referenceMetadata.uiProfiles` + `tests/fixtures/setup/*.json` |
 
-Data from all available server files is merged (union of all values). Hardcoded entries for protocols and widgets not found on any server are appended.
+`state.py` holds `OverkizState` + `OverkizAttribute`; `command.py` holds `OverkizCommand` + `OverkizCommandParam` (parameter values are harvested from discrete state values and command parameter enums). The `ExecutionMode` enum in `command.py` is hand-written and preserved across regeneration.
+
+Data from all available server files is merged (union of all values). The setup fixtures in `tests/fixtures/setup/` are merged in as an additional source: they capture real devices whose UI classes, widgets, classifiers and profiles (and states, commands, attributes) are not always exposed by the reference endpoints of the servers we have access to. Profiles found only in fixtures are added without details. `protocol.py` is the exception — Protocol members need the full `id`/`prefix`/`name`/`label` metadata, which fixtures don't carry, so they come only from `referenceMetadata.protocolTypes` plus the hardcoded `ADDITIONAL_PROTOCOLS`.
+
+Hardcoded entries for protocols and widgets not found on any server are appended (see `ADDITIONAL_PROTOCOLS` and `ADDITIONAL_WIDGETS` in the script). Discrete values that cannot form a valid Python identifier (e.g. the purely numeric `"1"`, `"2"`) are skipped and reported in the run output.
 
 ## generate_device_catalog.py
 

docs/ui-profiles.md

@@ -10,7 +10,7 @@ UI profiles describe device capabilities through the commands they accept and th
 !!! note
     This page is auto-generated. Run `uv run utils/generate_enums.py` to regenerate.
 
-**190 profiles** documented below.
+**192 profiles** documented below.
 
 ## AirFan
 
@@ -832,6 +832,10 @@ UI profiles describe device capabilities through the commands they accept and th
 | `start` |  | Start the default actuator behavior (movement, sound or timer) |
 | `stop` |  | Stop the current actuator behavior (movement, sound or timer) |
 
+## Startable
+
+*Details unavailable.*
+
 ## StatefulAirFan
 
 ### Commands
@@ -1767,6 +1771,10 @@ UI profiles describe device capabilities through the commands they accept and th
 |-------|------|-------------|
 | `core:StartedStoppedState` | `string` — `started`, `stopped` | Indicate if the sequence if started or stopped |
 
+## StatefulStartable
+
+*Details unavailable.*
+
 ## StatefulSwitchable
 
 ### Commands