Move 5 client error/friction callers off /api/internal/log-error to neutral ux-event path (adblock hardening)

Follow-up to the toast-beacon durable fix (SHA 9b6649f, VENUS-176 family). The adblock/filter-list magnet in the path name '/api/internal/log-error' also silently blocks the 5 OTHER CLIENT callers for any user with a privacy extension: error.tsx, global-error.tsx, client-error-reporter.tsx (client-ERROR reporting), log-guardrail.ts, log-action-error.ts. For an extension user these client errors + guardrail/actionError friction fail to log with no trace — undermines the no-silent-failure contract on the client leg. Fix = same proven pattern: point these 5 client callers at the neutral /api/internal/ux-event route (server-to-server callers of log-error stay put, unaffected by adblock). client-error reporters are highest value. Reversible + security-inert. BOUNDED — Elazar flagged spend; mars fenced the prior fix as 'not a telemetry refactor', so this needs an explicit go before dispatch.