fix(proxy): preserve negation in non-root sudo conditions

[Arnaud-IFEA]

Changes

• Fix sudo insertion for negated Bash if statements executed on remote servers through a non-root SSH user.
• Preserve the ! operator before sudo, producing if ! sudo docker ... instead of the invalid if sudo ! docker ....
• Add regression coverage for a simple negated condition and the proxy container removal pipeline.

Issues

• Fixes [Bug]: Proxy restart logs "sudo: !: command not found" for non-root SSH #11087
• Related to [Bug]: sudo-rs: '!': command not found #7622
• Related to [Bug]: Start Proxy and Restart Proxy fail on remote server — docker compose up is never executed (v4.0.0-beta.462) #8285

Category

• Bug fix
• Improvement
• New feature
• Adding new one click service
• Fixing or updating existing one click service

Preview

Before:

sudo: !: command not found
Waiting for container to be removed... (1/15)
...
Waiting for container to be removed... (15/15)

After:

Container removed successfully.
Proxy stopped successfully.
Container coolify-proxy Healthy
Successfully started coolify-proxy.

AI Assistance

• AI was NOT used to create this PR
• AI was used (please describe below)

If AI was used:

• Tools used: OpenAI Codex
• How extensively: Used to analyze the root cause, prepare the targeted code change, audit related sudo handling, and add regression tests. The behavior was manually reproduced and validated on a self-hosted Coolify instance.

Testing

• vendor/bin/pint --dirty --format agent passed under PHP 8.5.8.
• php artisan test --compact tests/Unit/ParseCommandsByLineForSudoTest.php passed: 51 tests, 109 assertions.
• Manually reproduced on Coolify 4.1.2, Debian 13.6, using a non-root SSH user with sudo.
• Confirmed that the proxy container is removed and restarted successfully after the fix.

Contributor Agreement

Important

• I have read and understood the contributor guidelines. If I have failed to follow any guideline, I understand that this PR may be closed without review.
• I have searched existing issues and pull requests (including closed ones) to ensure this isn't a duplicate.
• I have tested all the changes thoroughly with a local development instance of Coolify and I am confident that they will work as expected when a maintainer tests them.