Set upper limit on DuckDB version (<0.10.0) to avoid Arrow errors

[d33bs]

Description

This PR sets an upper limit of <0.10.0 on DuckDB to avoid Arrow errors. The change comes about as a result of discussions in #163 (thank you @shntnu!). It looks like a fix is forthcoming via changes related to duckdb/duckdb#11157 . Just the same, I wasn't sure which release might next include the fix, so I focused on stability for existing users / capabilities for now.

References #163

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.

[d33bs]

Thank you @gwaybio ! Going to merge this in. I've also labeled this as a patch release which will trigger v0.0.5 to be created on merge to help expedite reaching users with a fix.