Avoid get_dummies dtype change in pandas v2 (keep backwards compatible)

[lmmx]

• Data quality pandera example broken since pandas v2 #227

Changes

• The dtype argument has been added to all uses of get_dummies, as the default value changed in pandas v2

How I tested this

• python run.py no longer produces errors

Checklist

• PR has an informative and human-readable title (this will be pulled into the release notes)
• Changes are limited to a single goal (no scope creep)
• Code passed the pre-commit check & code is left cleaner/nicer than when first encountered.
• Any change in functionality is tested
• New functions are documented (with a description, list of inputs, and expected output)
• Placeholder code is flagged / future TODOs are captured in comments
• Project documentation has been updated if adding/changing functionality.

[skrawcz]

Awesome thanks for catching and fixing. One quick question -- is this backwards compatible with pandas <2.X? If not, we could just bump the pandas minimum for the example.

[skrawcz]

Actually just looked at the docs. The change in get_dummies was going from a default of unit8 to bool. So this will be backwards compatible with prior pandas versions.

[skrawcz]

FYI - #229