Localize queue: add filters (backend params + FilterPopover)

Context

While restyling the localize tables (#241), we agreed the /localize queue should get a Filters button like /classify and /localize/done. Postponed to its own PR because it needs backend work — GET /api/v1/sequences/localization-queue currently accepts only pagination params.

Scope

Backend — filter parameters on the localization-queue endpoint. Rows are alert-grouped ((source_api, platform_alert_id)), so filters apply to alert-level attributes:

• camera, organisation, source_api
• recorded_at date range

Frontend — reuse the FilterPopover UI on /localize (DetectionAnnotatePage), persisted via usePersistedFilters like the other list pages. Hide the sections that don't apply to a pre-annotation queue (model accuracy, FP types).

Decision record: chosen over client-side-only filtering (misleading with pagination) during the #241 design discussion.

Start with GET /api/v1/sequences/localization-queue, then inspect DetectionAnnotatePage, the shared FilterPopover, and usePersistedFilters as used by /classify and /localize/done. Done means alert-level camera, organisation, source_api, and recorded_at range filters work with pagination, persist on /localize, and omit model-accuracy and FP-type sections.