`local status -o X` should always emit valid yaml | json

[foxish]

./signadot local status -o json
Error: signadot is not connected

This is not valid JSON, which will make it hard to stitch this command into a workflow

[foxish]

cc @daniel-de-vera @scott-cotton

[foxish]

Same issue exists on connect and disconnect as well.

[scott-cotton]

It sounds like we might not have the same expectations, so I'd suggest discussing this issue more.

Here is what I'd expect for facilitating stitching this into a workflow:

1. -o refers to output, NOT stderr.
2. local status should NOT consider being disconnected an command invocation error, nor should it consider an error in communicating with locald a command invocation error, rather, these should be part of the status and local status should almost never exit non-zero.
3. Upon command invocation error, the error messages are placed on stderr, and the output is not necessarily coherent.
4. local connect and local disconnect should return errors/exit non-zero when already connected or respectively already disconnected to help the wrapper confirm the expected state.

For reference, here is a related issue to using the cobra framework.