Stdio command path resolve

[mpaquettePax8]

Fix command path resolution in StdioTransport

Problem

When using command-line extensions in Goose, the command path was being used as-is, which could cause failures when starting a Goose session from different directories since the paths were relative to the working directory.

Changes

• Modified StdioTransport::resolve_command_path() to properly handle relative paths
• When a command path is provided:
  • If it's absolute, use it as-is
  • If it's relative, resolve it against the current working directory to get an absolute path

Testing

Test cases to verify:

1. Absolute paths work as before
2. Relative paths (e.g. index.js) are correctly resolved against the working directory
3. Starting a Goose session from any directory works with the same extension configuration

[salman1993]

curious when you were running into this error - is it when using --with-extension option in the CLI?

[salman1993]

do we wanna check if this is a valid path?

[mpaquettePax8]

yeah could be slightly better to exit earlier here if the file doesnt actually exist rather than letting if fail later in spawn_process

will add a check and then also will fix the lint errors from cargo fmt

[mpaquettePax8]

curious when you were running into this error - is it when using --with-extension option in the CLI?

I havent tried the cli argument, I run goose configure and add a stdio command line extension, enable it when i start a session!