console: non-interactive lint recording

[hawkw]

I was talking to @olix0r about the console's new warnings feature, and he had a suggestion that seemed worth looking into: it would be cool to add a mode where the console CLI can output any lints detected to a file (maybe in JSON?). This could be coupled with the option to run the console non-interactively (no TUI) for a fixed period of time (or exit when the monitored program ends?).

The goal is to allow running a test workload, such as a load test, in a CI job, and fail if there are any warnings detected at runtime. This could also potentially be used in conjunction with unit testing.

It might also be nice to be able to save warning summaries while running interactively, so you can look back at what happened while you were interactively inspecting tasks. So, perhaps "non-interactive mode" and "record lints" should be separate options.

[BatmanAoD]

I would also appreciate a non-interactive mode, just to have a CI job that can validate that my service's console-subscriber setup is working. For now I am using grpcurl and jq with some basic assertions about WatchUpdates returning some tasks.