add basic usage report

[MattShirley]

Instead of limiting this report based on SQL rows as the Issue requested, I have added logic to SqlCsvReportView to allow a max size to be added to a report. Output will be truncated by row if the max download size is exceeded.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 89.62%. Comparing base (f06b45a) to head (d114e10).
⚠️ Report is 2 commits behind head on develop.

Additional details and impacted files

@@             Coverage Diff             @@
##           develop    #1495      +/-   ##
===========================================
+ Coverage    89.20%   89.62%   +0.42%     
===========================================
  Files          103      106       +3     
  Lines         3732     3953     +221     
  Branches       460      485      +25     
===========================================
+ Hits          3329     3543     +214     
- Misses         326      331       +5     
- Partials        77       79       +2     

☔ View full report in Codecov by Harness.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[ponyisi]

See the one thing, otherwise looks good to me

[MattShirley]

Hmm.. I wonder if there still needs to be a limit here in cases of large TransformRequest tables. How much memory do pods usually have in prod?

[ponyisi]

We would expect 2-3 GB?

[MattShirley]

I changed SqlCsvReportView to always stream results from the SQL server in 1000 row increments, so this shouldn't be a problem for general reporting. Expected large CSVs can just implement the max_download_size (which we can optionally add a default value, currently it's unbounded by default).

[ponyisi]

As discussed in the meeting earlier today - it might be nice to just dump everything present in the TransformRequest model (aka the requests table) instead of trying to be clever and cherry-pick?

[MattShirley]

As discussed in the meeting earlier today - it might be nice to just dump everything present in the TransformRequest model (aka the requests table) instead of trying to be clever and cherry-pick?

@ponyisi I updated the field list to include most fields on TransformRequest. I have still excluded some fields, such as database keys, the selection itself, and some of the longer fields that I wasn't sure would be useful. Can you take a look at that and tell me if you want it modified?