execute_safe_command should respect timeout_return

This fixes an issue where a command run by `execute_safe_command()` would timeout and the return code would be set to 2 (CRITICAL) rather than respecting the user defined `timeout_return` value set in the configuration.

I've tested this in production and confirmed the behavior matches what's expected.