Fix deprecated Posthog API Key initialization

[bryannho]

Describe your changes

• CLI was throwing an error when making telemetry calls due to the Posthog key not being initialized
• We can no longer set the posthog API key via posthog.project_api_key = self.api_key since its deprecated
• Updated the initialization to posthog.Posthog(api_key, host='https://us.i.posthog.com') and changed the log_api function to use this client

Issue number

Fixes support issue: https://ploomber-io.slack.com/archives/C08QNPDF15J/p1752779413170409

Checklist before requesting a review

• Performed a self-review of my code
• Formatted my code with pkgmt format
• Added tests (when necessary).
• Added docstring documentation and update the changelog (when needed)

---

📚 Documentation preview 📚: https://ploomber-core--91.org.readthedocs.build/en/91/

[edublancas]

let's look up in which posthog package version this was applied, and put it here:

core/setup.py

Line 18 in 3fdc748

"posthog",

like posthog>=x.y.z

also, the docs are failing because we're missing this: https://github.com/ploomber/jupysql/blob/6f83dbec7659124efe00c8ab1c3838b404fc0f3f/.readthedocs.yml#L24

the CI is also failing, I think because the Python versions are too old. let's only test with 3.10, 3.11 and 3.12

[edublancas]

the pin should be the other way around: >x.y.z

your previous changes were fine but we need to pin to ensure that the new version also forces a posthog upgrade

[bryannho]

Pinned the version to >=3.0

[bryannho]

@edublancas before I saw your review I went back and pinned the version instead of making the changes (since I saw the tests were failing due to PH not supporting python 3.8)

If you're okay with removing the python 3.8 tests then I'll bring back the original changes and apply your notes

[edublancas]

im ok removing old python versions

[bryannho]

Tests are failing due to failed mocks. Updating them now

[bryannho]

@edublancas please review again when you get the chance

[edublancas]

this isn't a good way to handle an incompatibilty, instead we can raise an error telling users they must upgrade posthog or downgrade ploomber-core

[bryannho]

Fixed: ca6301a