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

Is your feature request related to a problem? Please describe.
Currently in feature_store.yaml, we can only specify a region for DynamoDB provider. As a result, it requires an actual DynamoDB to be available when we want to do local development/testing or integration testing in a sandbox environment.

Describe the solution you'd like
A way to solve this is to let user pass an endpoint

On more advanced versions of LakeFS (probably > = v1.0.0), we would like to remove the logic that tries to fill the generation field in DB when loading old dumps. It means we will no longer support loading dump that made with a version lower than v0.61.0.

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

Summary

There is a typo in the output here: https://github.com/whylabs/whylogs/blob/mainline/src/whylogs/cli/demo_cli.py#L113

Also we can update this to better align with our examples and suggested use, e.g. we can remove prompting for 'project' and 'pipeline' since these aren't required, and streamline the script to simplify the demo experience.

Describe the bug
Currently, we have places in project where paged responses are returned with hardcoded hasNext and total properties. Need to fix this and return valid values to frontend. Frontend need to use these values instead of current solution

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