Fix multiline claude_args parsing issue with spaces in Bash tools (#844)

[jose-blockchain]

Summary

Fixes issue #844 where multiline claude_args with Bash tools containing spaces were incorrectly parsed by the shell-quote parser, causing arguments to be split at spaces.

Changes

1. Added detection logic to identify incorrectly parsed arguments (e.g., Bash(git without closing paren, or standalone command words after tool names)
2. Added warning when incorrect parsing is detected, guiding users to quote values with spaces
3. Updated documentation in migration guide to clarify quoting requirement for Bash tools with spaces
4. Added tests to verify the fix works correctly and warnings are triggered appropriately

Testing

All existing tests pass, and new tests verify:

• Quoted values with spaces parse correctly
• Unquoted values without spaces work as before (no false warnings)
• Warnings are triggered when incorrect parsing is detected

Solution

The fix detects common patterns of incorrect parsing and warns users. The proper solution (as mentioned in the issue) is to quote values with spaces, which now works correctly in both single-line and multiline YAML formats.

Fixes #844

[jose-blockchain]

please review @chrislloyd @dougbarth @bhuga if worth it.

[ashwin-ant]

I think this change isn't needed, we shouldn't have a package lock file at all since we have bun.lock