chore(python): Switch over some of the custom Python date/time conversions to native PyO3 conversions

[itamarst]

Fixes #16158

This should probably give a performance boost for relevant code, but I didn't check.

Things I didn't touch:

• PyArrow usages (logical_plan/pyarrow.rs), because I didn't understand what was going on there
• Calls from Python code to the old Python functions. These could in theory be switched to calling into Rust...
• Conversions that were deferred to Finish switching to PyO3 0.21's native datetime support, now available with abi3, once Python 3.9 is the minimum version #16199 due to Python 3.9 probably being required to do so.

[itamarst]

Tried nanoseconds here, it broke the tests, so stuck to micro/milliseconds only.

[codecov]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 81.03%. Comparing base (674a048) to head (07b5252).

❗ Current head 07b5252 differs from pull request most recent head e65955a. Consider uploading reports for the commit e65955a to get more accurate results

Additional details and impacted files

@@            Coverage Diff             @@
##             main   #16203      +/-   ##
==========================================
+ Coverage   80.93%   81.03%   +0.10%     
==========================================
  Files        1393     1393              
  Lines      179559   178941     -618     
  Branches     2907     2907              
==========================================
- Hits       145331   145013     -318     
+ Misses      33722    33423     -299     
+ Partials      506      505       -1     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[ritchie46]

Thanks! Can you rebase?

[itamarst]

@ritchie46 I fixed the conflict. If you literally want a rebase I can do that too.

[ritchie46]

Nope, the conflict is fine. ^^