Rollout --output-json and --output-yaml part 1

[newhoggy]

Changelog

- description: |
    Rollout `--output-json` and `--output-yaml` to various commands:
    * `compatible conway governance action view`
    * `compatible conway governance vote view`
    * `conway governance action view`
    * `conway governance vote view`
    * `conway query leadership-schedule`
    * `debug transaction view`
    * `latest governance action view`
    * `latest governance vote view`
    * `latest query leadership-schedule`
    * `query leadership-schedule`
    Ensure we encode json the same way in each command.
# uncomment types applicable to the change:
  type:
  # - feature        # introduces a new feature
  - breaking       # the API has changed in a breaking way
  # - compatible     # the API has changed but is non-breaking
  # - optimisation   # measurable performance improvements
  # - refactoring    # QoL changes
  # - bugfix         # fixes a defect
  # - test           # fixes/modifies tests
  - maintenance    # not directly related to the code
  # - release        # related to a new release preparation
  # - documentation  # change in code docs, haddocks...

Context

This helps keep output options of commands consistent.

How to trust this PR

Highlight important bits of the PR that will make the review faster. If there are commands the reviewer can run to observe the new behavior, describe them.

Checklist

• Commit sequence broadly makes sense and commits have useful messages
• New tests are added if needed and existing tests are updated. See Running tests for more details
• Self-reviewed the diff

[carbolymer]

Why aeson and not Json.encodeJson?

[newhoggy]

I was going to do it, but postponing to a future PR to avoid changing too much in the one PR so if something breaks it's easier to pinpoint the problem.