data-quality

Describe the bug
data docs columns shrink to 1 character width with long query

To Reproduce
Steps to reproduce the behavior:

1. make a batch from a long query string
2. run validation
3. render result to data docs
4. See screenshot
   <img width="1525" alt="Data_documentation_compiled_by_Great_Expectations" src="https://user-images.githubusercontent.com/928247/103230647-30eca500-4

The Stacktrace returned from failed API operations in the HadoopFS implementation loses some important context (Error message, HTTP status code, error body in the response - and request ID), making it very hard to debug configuration issues without tailing the log(s) of lakeFS server(s) itself.

We're using marshmallow to parse whylogs config from YAML

However, Pydantic is much more powerful as it allows users to set config via various mechanims, from YAML, JSON to Environment settings.

We should consider moving to pydantic

What type of re_data dbt macro you would like to add

• validate

What macro should be doing

Return true is string is a valid JSON and can be parsed to JSON

Motivation

As odd-platform supports redshift and so on, it would be awesome to support BigQuery integration.

What is the feature request? What problem does it solve?
We need to integrate some static code analysis in order to be able to better ensure code quality and security.

Suggested solution
In the current Github Org SonarCloud and/or Codecov are approved so we should use one (or both) of them.

Additional context
This also was found as a gap in the evaluation https://bestpracti