feat: Validate overrides key consistency for schema sampling

[MoritzPotthoffQC]

Motivation

When sampling for a schema by providing a sequence of mappings (rather than a mapping of iterables), the keys of the first mapping in the override dictate the schema of the data frame that is initialized to start sampling. This is currently not clearly documented.

While specifying different keys for the different entries can work out (e.g., by leaving out certain keys in following members, which are then imputed as None), it is pretty easy to add overrides keys to entries at indices > 0 which are not in the first entry. These will then silently be ignored. This can cause the sampling operation to fail (as it would need the overrides to find a compliant data frame) or (even worse) lead to a sampled data frame that does not comply with the expectations of the user.

Changes

• Explicitly validate that all entires in the overrides sequence specify the same keys
• Add test

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 100.00%. Comparing base (b711ac3) to head (3c9702c).
⚠️ Report is 1 commits behind head on main.

Additional details and impacted files

@@            Coverage Diff            @@
##              main      #165   +/-   ##
=========================================
  Coverage   100.00%   100.00%           
=========================================
  Files           51        51           
  Lines         2903      2907    +4     
=========================================
+ Hits          2903      2907    +4     

☔ 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.

[borchero]

Nice!