integration for `cabal`

## Summary

It would be nice to have a `cabal` integration, like `cabal audit` that can build a report for a cabal package, now that you can write plugins for `cabal`.

- [x] printing human readable
- [x] printing to json
- [ ] instead of running in `IO`, use more fine grained stack to allow some nice changes in a clean way, e.g. outputting without colouring, cf. https://no-color.org/
- [ ] querying for newer packages on hackage
- [ ] Add option `—dont-solve` that compares against the parsed version range in the stanza instead of solving the project. This would be useful for e.g. libraries
- [ ] pass through arguments from `cabal` and show `cabal` help text
- [ ] both for URI parsing (for `git clone` and filepath parsing, be clever about creating directories and showing errors
- [x] not planned ~~https://github.com/haskell/security-advisories/issues/166~~

Start by reviewing the existing cabal plugin integration and the completed checklist items for human-readable and JSON output. The remaining scope includes execution effects, Hackage queries, version-range handling, argument and help passthrough, URI and filepath parsing, directory creation, and error reporting; done is not clearly defined beyond addressing these items.

Written by the indexing model from the issue text.