PLUTO-101 follow-up: wire fn_getASolucionarBundle into app

Migration 071 (fn_getASolucionarBundle) landed on main (5c41a39), applied to prod, audit-pluto-ca PASSed the SQL review. Replace the 7-query mapWithConcurrency fan-out in src/app/(protected)/admin/a-solucionar/page.tsx loadAnomalies() with a single call-site in src/db/queries.ts invoking the bundle fn, keyed by the same 7 top-level JSON keys the page already expects (activeUsersForDomainCheck, docentesSinComision, alumnosSinAsignacion, sinRolActivo, comisionesSinJtp, comisionesSinAdjunto, alumnosSinPracticas). Note: the fn's activeUsersForDomainCheck section does NOT apply the JS-side isAllowlistedEmail filter that page.tsx currently applies post-fetch to section 1 only -- keep applying that filter after unwrapping the bundle, the fn intentionally does not replicate it. Class-S (app-only, no schema change).