Fix CLI exit code for failed commands

[ved1beta]

Fix CLI exit code for failed commands

The CLI was returning exit code 0 (success) even when commands like naptha run failed with errors. This is incorrect behavior, as command failures should return non-zero exit codes to properly signal failure to the calling process.

Changes

• Added error status checking in the run function for all module types (agent, tool, orchestrator, environment, kb, memory)
• When a module run completes with error status, it now raises an exception with the error message
• Improved error message formatting in the CLI to match the expected format
• Module type validation now properly raises an exception with non-zero exit code

Testing

Verified that:

• Successful commands continue to return exit code 0
• Failed commands (like Server 500 errors) now correctly return exit code 1
• Error messages maintain the format shown in the issue

This fix ensures shell scripts and automation tools can properly detect when Naptha commands fail, allowing for better error handling in CI/CD pipelines and scripts that use the Naptha CLI.

fix #130