Parsing errors should display the offending file information

[afeld]

At the moment, the error is surfaced, but there isn't enough information there to know how to fix the problem. Example:

(cg-compliance) $ compliance-masonry docs gitbook FedRAMP-moderate
Schema Version can not be found.

In increasing order of usefulness, these errors should also include:

1. The name of the component
2. The path of the file
3. The URL to the file, if it's included via a dependency
4. The line number

[jcscottiii]

Most of this covered by #189

Only number 3 isn't. Does it still matter @afeld?

[afeld]

I would say 3 is a nice-to-have...happy to break out to a separate issue if you like.

[git-ingham]

As someone trying to get this working at all, I second this request. Tracking down errors is more of a guess than a productive endeavor.