Overhaul doctor run output to focus on user experience

[technicalpickles]

I think I have worked with enough scope scripts + configs to get a decent feel for it. I'd like to take some time to figure out what the idea output users see when they are running this command. I think the current view is very log-centric as in tracking what happened, which makes sense considering it's using the tracing library.

Here's what output looks like now:

[technicalpickles]

I was playing around with TextEdit, and coloring the output. Thinking about something more like:

It does imply a few changes:

• either using some other output facility, or customize info!'s event formatter
• run check first and display part of a line, then output the status with a newline
• split logging that a check ran from the fix running
• re-run the check after a fix is attempted

I'm not as solid on that last summary line. Like if something is successfully fixed, do you list it as fixed AND successful? Maybe not as useful.

The text for reference

Checking `Homebrew`... OK
Checking `~/.gusto/init.sh`... OK
Checking `rbenv`... OK
Checking `GitHub CLI`... OK
Checking `GitHub SSH Authentication`... OK
Checking `AWS SSO`... PROBLEM
Trying to fix `AWS SSO`...
Signing in... keep an eye out for the browser window

Attempting to automatically open the SSO authorization page in your default browser.

If the browser does not open or you wish to use a different device to authorize this request, open the following URL:
https://device.sso.us-west-2.amazonaws.com/
Then enter the code:
ABCD-EFG

Successfully logged into Start URL: https://gusto.awsapps.com/start
Rechecking AWS SSO... OK

Summary: 1 FIXED, 7 OK