URGENT: fix quoted search_path in mig 099/102 -- 33 functions broken, prod outage since 13:03 UTC

Live prod outage, root cause measured by coder-pluto-cc 2026-07-31: migrations 099 and 102 wrote ALTER FUNCTION ... SET search_path TO 'public, pg_temp' with the value single-quoted, making it ONE identifier instead of a two-element list -- SET search_path TO 'public, pg_temp' yields current_schemas(false)={} (empty), vs unquoted SET search_path TO public, pg_temp yielding {public}. Every one of 33 affected functions (fn_addUserRole, fn_bulkAssignRole, fn_setPrimaryRole, fn_recomputePrimaryRole, fn_preventLastAdminRemoval, fn_preventNestedPersona, fn_detectAdminAccountEdit, fn_forbidAdjuntoJtpOverlap, fn_resolvedataaccessscope, isUserRowSafeToSupersede, all 23 fn_archive_*/fn_archivePractica* triggers) has resolved NOTHING since mig 099 applied 13:03 UTC (7bd764b) / 102 at 13:39 UTC (6684a00) -- every table ref inside them errors relation-does-not-exist. Broke /practicas /informes /alumnos /practicas/nueva reads and now practicaCreateFailed (archive triggers in the broken set). Guards fail CLOSED (availability incident, not a security bypass) per coder-pluto-cc's severity read. Detector: EXISTS (SELECT 1 FROM unnest(proconfig) c WHERE c LIKE 'search_path="%') -- NOT a match on cron_auth_header's {search_path=pg_catalog, vault} (that's a real 2-element array, no embedded escaped quote).