Bash sandbox execution path — mostly cosmetic variable churn, no clear functional change

The code that runs bash commands, sandboxed or not, has had many of its internal variable names changed around building filesystem allow/deny lists, registering network access lists, and spawning subprocesses with telemetry. The underlying logic, including how write access is denied by default (keepBaseDenyWrite) and read access can be dropped (dropAllowRead), tracking of the working directory, and telemetry attributes, appears unchanged.