chore: update LaunchDarkly AI SDK dependencies to latest compatible versions

[devin-ai-integration]

Summary

Bumps the LaunchDarkly SDK dependency floors across all 10 examples to the latest compatible versions. No source-code changes were required — the examples already use current APIs and no deprecated APIs were found.

launchdarkly-server-sdk-ai and launchdarkly-observability are on their 1.x line (per reviewer feedback, rather than left on pre-1.0 pins). launchdarkly-server-sdk-ai-openai and launchdarkly-server-sdk-ai-langchain have no 1.x release yet, so they track their latest (0.x) release.

Version changes (floor bumps; >= style preserved, <2.0.0 caps kept/added on the 1.x packages):

Package	Before (main)	After	Latest on PyPI
launchdarkly-server-sdk-ai	>=1.0.0,<2.0.0 (features) / >=0.20.0 (rest)	>=1.2.0,<2.0.0 (all)	1.2.0
launchdarkly-observability	>=0.1.0	>=1.2.4,<2.0.0	1.2.4
launchdarkly-server-sdk-ai-openai	>=0.5.0	>=0.7.0 (no 1.x published)	0.7.0
launchdarkly-server-sdk-ai-langchain	>=0.6.0	>=0.8.0 (no 1.x published)	0.8.0

Testing

• poetry install succeeds for the examples (matches CI's build-and-run job, which is install-only). Resolved: launchdarkly-server-sdk-ai 1.2.0, launchdarkly-observability 1.2.4, launchdarkly-server-sdk-ai-openai 0.7.0, launchdarkly-server-sdk-ai-langchain 0.8.0.
• Ran the create_model example against a test SDK key: the SDK initialized successfully (*** SDK successfully initialized) and fetched the AI config from LaunchDarkly. No deprecation warnings.

Caveats

• End-to-end model runs require third-party provider credentials (OpenAI / AWS Bedrock / Gemini) not available in this environment, so full provider calls were not exercised. CI only runs poetry install, which passes.
• Lock files are gitignored in this repo, so none are committed.

Link to Devin session: https://app.devin.ai/sessions/3e5d28b3d26b4951aed3bd430aee5ad3

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment, CI, and merge conflict monitoring

[jsonbailey]

We should look at updating these to the 1.0 versions rather than leaving them on pre-release.

[devin-ai-integration]

Done in e67c041. Moved both onto their 1.x lines across all examples: launchdarkly-server-sdk-ai → >=1.1.0,<2.0.0 and launchdarkly-observability → >=1.2.4,<2.0.0.

launchdarkly-server-sdk-ai-openai (0.7.0) and launchdarkly-server-sdk-ai-langchain (0.8.0) have no 1.x release published on PyPI yet, so I left them tracking their latest 0.x. Happy to bump those too once 1.x ships. poetry lock/install still pass for all 10 examples.

[devin-ai-integration]

Closing: no update needed. Every bumped floor is already satisfied by the existing constraints — the old floors (launchdarkly-server-sdk-ai >=1.0.0/>=0.20.0, launchdarkly-observability >=0.1.0, -ai-openai >=0.5.0, -ai-langchain >=0.6.0) all already permit the current latest releases (1.2.0 / 1.2.4 / 0.7.0 / 0.8.0), and no sub-package requires a higher floor (the openai/langchain extensions only require launchdarkly-server-sdk-ai>=1.0.0). With no committed lockfile, poetry install already resolves to the latest compatible versions, so no floor bump is warranted.