Scan floating IPs in the background, page by page, so thousands of addresses work

The "Scan Floating IP" button failed with a client timeout: the project now
holds ~6.4k floating IPs and the scan listed them all in one unpaginated,
timeout-less Neutron request on the HTTP request context.

openstack: ListFreeFloatingIPs reads marker-based pages (fields= keeps them
small) with per-page retry/backoff on transport errors, 5xx and 429, and every
request now has a timeout (also ends hangs inside the orchestrator tick).

orchestrator: the scan is a single-flight background job on the process
context with progress (clearing/listing/enqueuing/done/error), dry_run, full
discovery before anything is enqueued, then SubmitIPs in chunks of 500 in
ascending IP order; a failed read leaves the queue untouched. The auto-cycle
gets a "scanning" phase that polls the job, so the control loop and
autoCycleMu are never held across OpenStack/DB work; it recovers after a
restart and waits for (instead of adopting) a scan started by someone else.

db: migration 0009 (indexes), paged ListIPsPage/ListRegistryPage, GROUP BY
counters, EXISTS completion check, set-based ClearAllIPs.

API: POST /admin/ips/scan -> 202 (dry_run, wait), GET /admin/ips/scan, paging
and filters on /admin/ips and /admin/registry (bare arrays without limit),
results_by_overall in /admin/status.

dashboard: scan progress panel and dry-run button, paginated /ips and
/registry with server-side filters, Overview on counters and capped lists
with progress/ETA, "select all N by filter", hx-params fix for per-row
buttons, real counts in confirmations.

Also: docs (API, USAGE, DASHBOARD, README), plan and review under
docs/changes/, bin/ rebuilt with new SHA256SUMS.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>

configs/control-api.example.yaml

@@ -37,6 +37,20 @@ openstack:
   user_domain_name_env: "OS_USER_DOMAIN_NAME"
   password_env: "OS_PASSWORD"
 
+  # Постраничное чтение Floating IP (скан при тысячах адресов): сколько
+  # адресов запрашивать у Neutron за один запрос. Default 200.
+  # Page size of the paged floating-IP listing. Default 200.
+  list_page_size: 200
+  # Таймаут каждого HTTP-запроса к Keystone/Neutron, секунд. Default 60.
+  # Per-request HTTP timeout (also protects the orchestrator tick from a
+  # hung Neutron call). Default 60.
+  request_timeout_seconds: 60
+  # Сколько раз повторять неудавшуюся страницу (сетевая ошибка, EOF/
+  # RemoteDisconnected, 5xx, 429) с паузами 1,2,4,8,16 с. Default 5;
+  # отрицательное значение отключает повторы.
+  # Retries per failed listing page. Default 5; negative disables retries.
+  list_page_retries: 5
+
 # Аутентификация API: здесь только ИМЕНА переменных окружения, значения
 # (статические bearer-токены) задаются окружением процесса — см.
 # deploy/systemd/control-api.service (EnvironmentFile=). Генерация:
@@ -76,6 +90,10 @@ orchestrator:
   # scan on demand via POST /api/v1/admin/ips/scan or the dashboard's
   # "Scan Floating IPs" button.
   fip_scan_interval_seconds: 0
+  # Общий таймаут одного фонового скана Floating IP (очистка + чтение всех
+  # страниц + постановка в очередь), секунд. Default 1800.
+  # Overall deadline of one background floating-IP scan. Default 1800.
+  fip_scan_timeout_seconds: 1800
 
 aggregation:
   missing_counts_as_fail: true