FOUR-32613 - Realtime (or at least faster) script executor - #8997

Requires: https://github.com/ProcessMaker/script-executor-service/pull/420

ProcessMaker counterpart to SES realtime executors. New executor type Realtime: customer-owned Dockerfile, dedicated Horizon queue, synchronous SES call, result shown in the script editor (with duration).

Pairs with script-executor-service spike/FOUR-32613-C.

Why

Same as SES: faster script runs, customers own the base image and can customize freely. SES does docker run --rm -i with JSON on stdin; PM just has to create the executor, route jobs, and treat the HTTP response as the result (no callback wait).

Executor type + admin UI

ScriptExecutorType::Realtime. Creating one sends realtime: true to SES with the full Dockerfile in config.

Admin language list adds php / python / javascript (realtime) with example Dockerfiles from resources/script-executors/realtime/*.Dockerfile (bootstrap reads stdin, evals/execs, prints JSON, exits). Customers edit that Dockerfile however they want.

Queue

New Redis connection redis-realtime and Horizon supervisor supervisor-realtime (auto balance, 2–20 processes). Preview, Execute, and BPMN RunScriptTask all onConnection('redis-realtime')->onQueue('realtime') when the executor is realtime.

The runner always sends sync: true to SES. TestScript formats the microservice payload locally (no callback) and broadcasts via Echo, including duration.

Other

• Keycloak access tokens for SES were already cached; that matters more now that every preview/run is a sync HTTP call.
• Script editor shows run duration.

Test plan

• Create a realtime executor from an example Dockerfile; SES build succeeds
• Script editor Test runs on the realtime queue and shows output + duration
• A process script task with a realtime executor also uses that queue
• Classic custom/system executors still use bpmn and the callback path