fix: log debug output when commands fail

[rupayon123]

Fixes #73

Debug mode now logs the command details before re-raising RubyShell::CommandError, so failed commands still show what ran. I also included stderr in the debug output, as requested in the issue thread.

Checks:

• ruby -c lib/rubyshell/debugger.rb
• ruby -c lib/rubyshell/error.rb
• ruby -c spec/debugger_spec.rb
• manual debug failure check with ruby -Ilib

I could not run the full RSpec file locally because the rspec executable is not installed here.

[albertalef]

Hi!! Sorry for the delay. Im reviewing now

[albertalef]

In some situations on the past, i had some troubles with errors losing data when rescued.

This actual code will not give us problems, but. Lets add a test checking that when we have a command being rescued outside, with debug option true, the returned CommandError has the correct attributes. Like:

begin
  ls('error', _debug: true)
rescue => e
  puts e.command # => Correct command
  puts e.stdout # => Correct stdout
  # etc
end

[albertalef]

Nice! Now, check the cicd, there is some failures

[albertalef]

We can separate the run_failed_debug_command on before blocks and distinct contexts, instead create a method to execute the code. To follow the idiomatic idea of rspec