refactor(pandas): enable copy_on_write for Pandas

[d33bs]

Description

This PR adds a configuration module and setting for Pandas (copy_on_write) which will eventually be turned on by default in Pandas >= 3.0.0 . Besides proactively avoiding issues with upgrades to Pandas, there are also possible performance benefits to doing this early (as per Pandas documentation on copy_on_write). I made these changes based on tests which were failing and noted in #366 .

After making this change, there are new test warnings concerning PerformanceWarning: DataFrame is highly fragmented. which may be worth investigating as part of this issue or possibly a new issue.

Closes #366

What is the nature of your change?

• Bug fix (fixes an issue).
• Enhancement (adds functionality).
• Breaking change (fix or feature that would cause existing functionality to not work as expected).
• This change requires a documentation update.

Checklist

Please ensure that all boxes are checked before indicating that a pull request is ready for review.

• I have read the CONTRIBUTING.md guidelines.
• My code follows the style guidelines of this project.
• I have performed a self-review of my own code.
• I have commented my code, particularly in hard-to-understand areas.
• I have made corresponding changes to the documentation.
• My changes generate no new warnings.
• New and existing unit tests pass locally with my changes.
• I have added tests that prove my fix is effective or that my feature works.
• I have deleted all non-relevant text in this pull request template.

[kenibrewer]

LGTM. Thanks for making this proactive change here!

[d33bs]

Thanks @kenibrewer , merging this in!