Make reports compatible with composite keys

[frances-h]

Resolve #835

[codecov]

Codecov Report

❌ Patch coverage is 97.43590% with 1 line in your changes missing coverage. Please review.
✅ Project coverage is 95.74%. Comparing base (cec3fa4) to head (3085bc5).
⚠️ Report is 1 commits behind head on feature/composite-keys.

Files with missing lines	Patch %	Lines
.../reports/single_table/_properties/data_validity.py	83.33%	1 Missing ⚠️

Additional details and impacted files

@@                    Coverage Diff                     @@
##           feature/composite-keys     #862      +/-   ##
==========================================================
- Coverage                   95.74%   95.74%   -0.01%     
==========================================================
  Files                         117      117              
  Lines                        4934     4955      +21     
==========================================================
+ Hits                         4724     4744      +20     
- Misses                        210      211       +1     

Flag	Coverage Δ
integration	81.21% <92.30%> (+0.34%)	⬆️
unit	84.46% <89.74%> (-0.02%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 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.

[sarahmish]

Looks good to me, I just wonder about the one comment in terms of error description.

[frances-h]

Fixes a test error on minimum versions: union on older versions of pandas doesn't treat NaNs as a single value so if a column has a null category, duplicate indices get created. Adding the drop_duplicates call removes the duplicated indices.

[pvk-developer]

LGTM!