feat(cargo-shuttle): use stderr, better error

[jonaro00]

(breaking): moved outputs from stdin to stderr

[greptile-apps]

PR Summary

This PR improves error handling and output stream management in the Shuttle CLI by directing warnings and status messages to stderr while keeping actual command output on stdout.

• Optimized workspace_path in ProjectArgs to return both path and metadata, eliminating redundant metadata fetches
• Improved error messaging for missing Rust projects with clearer context in args.rs
• Consolidated API URL validation logic within API client initialization block in lib.rs
• Fixed project rename output formatting and deployments list pagination handling

_{5 file(s) reviewed, 2 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

PR Summary

(updates since last review)

This PR continues to improve error handling and output management in the Shuttle CLI, with these key changes:

• Fixed typo in URL scheme error message in init.rs from "of" to "or", providing clearer guidance when unsupported URL schemes are encountered
• Simplified workspace_path() method in ProjectArgs to return only the path instead of a tuple with metadata, making the API cleaner
• Updated workspace path handling across config.rs to align with the simplified workspace_path() return type
• Removed tuple destructuring in config methods to match the new workspace path resolution approach

The changes focus on making error messages more user-friendly and simplifying the internal API for workspace path handling, though introducing a potential performance consideration with separate metadata calls.

_{4 file(s) reviewed, 2 comment(s)
Edit PR Review Bot Settings | Greptile}

[greptile-apps]

PR Summary

(updates since last review)

This PR adds a clarifying comment in args.rs about the necessity of a second cargo metadata call in the workspace root, with the following key change:

• Added documentation in ProjectArgs::project_name() explaining why a second metadata call is needed when run from a workspace member vs root

The comment helps future maintainers understand why an apparently redundant metadata call is actually necessary for correct workspace handling.

_{1 file(s) reviewed, no comment(s)
Edit PR Review Bot Settings | Greptile}