Telemetry opt-out not propagated to Python engine sidecar

[suryaiyer95]

When a user disables telemetry via the config file (telemetry.disabled: true in altimate-code.json), the Python altimate_engine sidecar spawned by the bridge is unaware — it calls altimate_core.init() without the disable flag, so telemetry still fires from the engine process.

Expected: disabling telemetry in altimate-code should also suppress telemetry in the engine subprocess.

Fix: inject ALTIMATE_TELEMETRY_DISABLED=true into the child process environment before spawning.