`bundle install` step is assumed to have succeeded when OOM killed

I have a Rails app that when deployed, runs the command

```
cd /home/app/staging/releases/20250304094541 && /usr/bin/env bundle install --jobs 4 --quiet
```

on the server. Due to `--jobs 4` and the amount of memory available, it happens to be OOM-killed.

SSHKit happily assumes it has succeeded and continues, erroring on a follow-up step.

My suspicion is that this commented-out code points into the direction of a solution: https://github.com/capistrano/sshkit/blob/master/lib/sshkit/backends/netssh.rb#L160-L166

Inspect lib/sshkit/backends/netssh.rb around lines 160-166, where the issue notes commented-out handling related to command status. Start by tracing how Net::SSH command failures are reported for the bundle install invocation, then verify that an OOM-killed command is treated as failed and prevents follow-up deployment steps.

Vom Indexierungsmodell aus dem Issue-Text verfasst.