refactor(litespeed): drop setUIDMode for shared lsphp + cut opcache 128→32M

OLS runs as the customer user end-to-end (server-level user/group set by
create-vhost-litespeed.sh), so lsphp inherits that uid without per-request
suEXEC. Eliminates the per-httpd-worker lsphp instance fan-out — one shared
lsphp parent now serves all httpd workers via the shared socket.

Combined with opcache.memory_consumption 128→32M, brain-jar measured shmem
dropped from ~880 MiB → 32 MiB and memory.current from ~1.1 GiB → 67 MiB
at the 1.5 GiB cap. No new oom_kills since the change.

Safe because cac-litespeed is one-customer-per-container — the container
boundary is the privsep boundary.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

configs/litespeed/lsphp-overrides.ini

@@ -25,9 +25,14 @@ session.gc_divisor = 1000
 session.gc_maxlifetime = 1440
 
 opcache.enable = 1
-opcache.memory_consumption = 128
+; Sized small because shmem is per-process-RSS on Linux cgroups (vs PHP-FPM's
+; COW-shared model). At 128 MB × N lsphp instances we were hitting 800+ MiB
+; shmem on heavy WP sites; 32 MB × N fits comfortably and still caches ~4000
+; scripts (covering Divi + WC + WP core easily). Bump per-site via WHP user
+; variables (OPCACHE_MEMORY_MB) if a high-traffic site needs more.
+opcache.memory_consumption = 32
 opcache.interned_strings_buffer = 8
-opcache.max_accelerated_files = 10000
+opcache.max_accelerated_files = 4000
 opcache.revalidate_freq = 60
 opcache.enable_cli = Off