Task: Decide fate of 11 hand-written Qt list entities silently capped at 100 rows

Decide and act on one of two paths for each of the 11 hand-written, model-less Qt list entities silently capped at 100 rows: (a) migrate each to a real codegen .org model (bringing has_pagination support "for free" alongside every other codegen benefit), or (b) hand-patch just the offset/limit-sending logic into the existing hand-written Client*Model.cpp without a full codegen migration, if that's judged lower-risk/cheaper for some or all of them. Not calendar-specific – filed under this story only because it was discovered while scoping the has_pagination pagination-truncation task.

Entities: role, system_setting (ores.iam=/=ores.variability), dataset, dataset_dependency, methodology, nature_dimension, origin_dimension, treatment_dimension, coding_scheme, coding_scheme_authority_type (ores.dq), telemetry_log (ores.telemetry).

This is explicitly lower priority than the misleading-pagination-UI bug the has_pagination task fixes: none of these 11 show a PaginationWidget at all, so there is no false affordance – a user sees a flat list and has no reason to expect more than what's shown.

• [ ] For each of the 11 entities, an explicit decision recorded: migrate to a codegen model, hand-patch pagination directly, or leave as-is (with a stated reason, e.g. "row count will never realistically exceed 100").
• [ ] Whatever's chosen is implemented and verified per-entity: the list window's PaginationWidget (if added) or the existing flat list correctly reflects the server's real row count, not a silently-capped page.
• [ ] Full local build green; ctest green.

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

Manual QA scenarios (scaffolded via compass add test_scenario, run through the QA Validation Runner panel) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.