## Summary
- write generated Python reference docs with explicit UTF-8 encoding
## Problem
`Path.write_text()` uses the platform default encoding if none is
specified. The generated reference content can include non-ASCII text,
so this docs generator can behave differently on Windows or other
non-UTF-8 locales.
## Before / After
Before: generated `.mdx` reference files were written with the process
default encoding.
After: generated reference files are always written as UTF-8.
## Verification
- `python -m py_compile docs/scripts/generate_python_reference.py`
## Description of changes
_Summarize the changes made by this PR._
- Improvements & Bug fixes
- ...
- New functionality
- ...
## Test plan
_How are these changes tested?_
- [ ] Tests pass locally with `pytest` for python, `yarn test` for js, `cargo test` for rust
## Migration plan
_Are there any migrations, or any forwards/backwards compatibility changes needed in order to make sure this change deploys reliably?_
## Observability plan
_What is the plan to instrument and monitor this change?_
## Documentation Changes
_Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the [docs section](https://github.com/chroma-core/chroma/tree/main/docs/docs.trychroma.com)?_
Rolly Calma