[Data Checks Improvement]: Optional strings that describe the test case

[fbertsch]

What is the issue?

When there are multiple test cases, or complicated ones, it can take time to skim through and understand what the test case is accomplishing. If instead we included optional strings that printed out if the test failed, we could very easily understand what tests are doing and why they might have failed.

For example, I have the test:

#fail
{{ min_row_count(10000, "as_of_date = @submission_date") }}

If this fails, it will get an error like Min Row Count Error: 126 rows found, expected more than 10000 rows".

But if I had a string to define the test, I could annotate it in the code and in the failure:

#fail
{% set check_str="Each day should have more than 10k updated clients" %}
{{ min_row_count(10000, "as_of_date = @submission_date", check_str) }}

Which might fail with:

FAILED: Each day should have more than 10k updated clients
Min Row Count Error: 126 rows found, expected more than 10000 rows.

This would also help ID which min_row_count check failed, when I have multiple.

How can we reproduce the bug

No response

┆Issue is synchronized with this Jira Task

[fbertsch]

Also see: https://github.com/mozilla/bigquery-etl/pull/4868/files#diff-7f709fb2a5dd43c9e768c5fbe6b0d750bc6528813580b3f7cbf9d0be59b9cc77R7-R20