Standardize output for installs

[RamblingCookieMonster]

At the moment, installs just spit out whatever output happens to be emitted from the dependency script. Ideally, that output could be shuffled to the verbose stream, and a consistent, passthru-esque object could be emitted. This would look cleaner and where needed, allow programmatic use of output.

[RamblingCookieMonster]

Some quick thoughts, current state is quite ugly with some types killing output, other types giving way too much output, etc.

• Include all Dependency metadata
• Include a Status boolean, depending on whether the install was a success (as much as we can tell)
• Include a StatusDetail (not tied to the name) string, which expands on Status:
  • If we failed, try to include a friendly description of why it failed and potentially how to fix - otherwise, text of whatever unexpected error we caught.
  • If we succeeded, indicate how - e.g. dependency already existed, or we used whatever method the dependency script called for
• Include a Output string, including output from whatever tool the script calls (in case the user
• Maybe include a property for each stream (Output, Error, Warning)? Always handy to have raw data from these streams, as well as some distilled bit (StatusDetail)
• Use format data to limit to something like Dependency Name, Dependency Type, Status, StatusDetail, letting folks explore as needed

Anything else? Is this too much?

Cheers!

[github-actions]

This issue has had no activity for 60 days. It will be closed in 30 days unless there is new activity or a maintainer removes the stale label.