fix: add autorestart to supervisord for process resilience

[mehmetkr-31]

Summary

Adds autorestart=true to both [program:base-consensus] and [program:op-execution] sections in supervisord.conf.

Problem

By default, supervisord uses autorestart=unexpected, which only restarts a process when it exits with a non-zero exit code. This means that if a process is terminated gracefully (e.g., by a SIGTERM during a Docker daemon event or internal crash that returns 0), supervisord will not restart it, leaving the node partially or fully offline until manual intervention.

Solution

Explicitly set autorestart=true for both programs. This ensures that the consensus and execution clients are automatically restarted regardless of how they exit, improving node reliability during long-running operations.

Impact

• Improves operational resilience for node operators running the Docker setup.
• Reduces manual intervention when a client process terminates unexpectedly.

Checklist

• Change is minimal and focused.
• No breaking changes to existing behavior.
• Verified that supervisord syntax remains valid.

[cb-heimdall]

🟡 Heimdall Review Status

Requirement	Status	More Info
Reviews	🟡 0/1	Denominator calculation Show calculation 1 if user is bot 0 1 if user is external 0 2 if repo is sensitive 0 From .codeflow.yml 1 Additional review requirements Show calculation Max 0 0 From CODEOWNERS 0 Global minimum 0 Max 1 1 1 if commit is unverified 0 Sum 1