Link to docs on status errors

[jonabc]

This branch/PR is based off of the docs updates at #380.

The linked updates to documentation mean that the tool can start to promote better self-serve resolution to compliance problems. As a first step, status failures should be linking to the help documents in order to help new users diagnose and hopefully fix any encountered errors.

I originally tried to keep the changes small, since the only product focused change here is to print a message like "see the docs" when the status command found errors. That became difficult and I found myself having to build workarounds because the existing way that reporters and commands interacted involved lots of block yielding and was generally more complex than it needed to be. I decided to rewrite the reporter system to make things simpler, which made adding this new functionality much easier as well.

The reporter and command changes largely amount to two things

1. Creating report objects in the command class and passing them into reporters. This focuses the reporter into only focusing on how to output information that is gathered in the report object during command runs

• this puts the command class in control of when report objects are created and when the reporter methods are called

1. Breaking the nested yield pattern that was used in commands and reporters. Reporter objects can now implement begin and end hooks for each of command, application, source and dependency as needed to output information. It's now simpler to write command methods because there is less use of yielded blocks to add or override functionality