Regression v1.205.0: nested `atmos workflow` call hangs at "Loading..." when workflow name is omitted (worked in v1.204.0)

### Describe the Bug

In Atmos v1.205.0 and above, calling `atmos workflow` from inside another workflow step can hang showing "Loading..." when the nested invocation omits the workflow name argument. This same workflow pattern completes in v1.204.0.

### Expected Behavior

Nested workflow invocation should:
- either error immediately with a clear message about the missing workflow name, OR
- reliably show an interactive selector and accept input when running in a workflow step.

### Steps to Reproduce

1. Create a workflow like:

```yaml
name: "01-set-stack"
workflows:
01-set-stack:
steps:
- name: set-stack
type: shell
command: |
#!/bin/bash
stack=$(atmos list stacks 2>/dev/null | fzf --prompt="Select an Atmos Stage: ")
echo "You selected: ${stack}"
STACK=${stack} atmos workflow -s ${stack}
```

2. Run atmos workflow

### Screenshots

_No response_

### Environment

_No response_

### Additional Context

_No response_