`limactl list` produces different data for `json` vs. `yaml` output

[jandubois]

I'm working on adding some integration tests and found that the limactl list command outputs different structures for json vs. yaml format:

All of the "host" setting use different names:

❯ l ls default --format json | yq .HostOS
darwin

❯ l ls default --format yaml | yq .hostos
darwin

Same for HostArch, LimaHome, and IdentityFile. Arguably these settings belong in the limactl info output because they are not specific to the instance.

In the YAML output all the instance specific settings are inside an instance object, but in the JSON they are merged together with the host settings.

❯ l ls default --format json | yq .name
default

❯ l ls default --format yaml | yq .instance.name
default

Returning different schemas for different formats is insanity, but I have no idea how to fix it while preserving backwards compatibility. If we do break compatibility, then we should probably do this in the 2.0 release, so I'll mark this as a high priority issue.

[jandubois]

Here is my suggestion:

• We add the 4 host settings to limactl info output
• We leave the JSON output unchanged for backwards compatibility
• We get rid of the instance object in YAML and move all fields up one level
• We rename the host fields in the YAML output to match the JSON names
• We document that the host settings may be removed from limactl list in Lima 3.0

I would like to remove the host settings, but think we should keep them for backwards compatibility. With this proposal the JSON output will remain unchanged, and I suspect that JSON is more likely to be used than YAML here.

[afbjorklund]

I think you can go ahead and break (fix?) the YAML output