Descriptive error with exact path in json

[ankuagarwal]

• Please check if the PR fulfills these requirements

• [x] Tests for the changes have been added (for bug fixes / features)
• [x] Docs have been added / updated (for bug fixes / features)

• What kind of change does this PR introduce? (Bug fix, feature, docs update, ...) Feature

• What is the current behavior? (You can also link to an open issue here) Currently we get all the error message caused in a file. It is difficult for user to pin point the exact location.

• What is the new behavior (if this is a feature change)?

• Adding an Error object containing the descriptive message, and the path in json where the error has occurred.
• Renaming ReportRunner to ReportGenerator, Instead of passing LintRunner, we pass the error data, and we get the final report.

• Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?) Updated Doc for more info.

• Other information: