Creating a detailed stats table for capturing details on the execution of dq rules.

detailed stats table for capturing details on the execution of dq rules

Description

https://github.com/Nike-Inc/spark-expectations/issues/55

Motivation and Context

As of now, the stats table details are not sufficient to get detailed insights on the rules executed. This PR provides more details using a detailed stats table on the execution of all the rules in a relational format.

How Has This Been Tested?

The testing was done in local env with the sample data provided with this framework.

Screenshots (if appropriate):

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Nike-Inc / spark-expectations

Creating a detailed stats table for capturing details on the execution of dq rules. #80