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, staying within each currently-configured major version. No source-code changes were required — the examples already use current APIs and no deprecated APIs were found.

Version changes (floor bumps; >= style and existing <2.0.0 caps preserved):

Package	Before	After
launchdarkly-server-sdk-ai (feature examples)	>=1.0.0,<2.0.0	>=1.1.0,<2.0.0
launchdarkly-server-sdk-ai (getting_started + create_judge)	>=0.20.0	>=0.20.1
launchdarkly-observability	>=0.1.0	>=0.1.1
launchdarkly-server-sdk-ai-openai	>=0.5.0	>=0.7.0
launchdarkly-server-sdk-ai-langchain	>=0.6.0	>=0.8.0

Floors were bumped only to the latest release within the same major as each existing floor (never crossing a major boundary, never widening below the existing minimum). Constraints remain open-ended, so poetry install resolves to the newest published releases.

Testing

• poetry install succeeds for all 10 examples (matches CI's build-and-run job, which is install-only).
• Resolved latest versions confirmed: launchdarkly-server-sdk-ai 1.1.0, launchdarkly-observability 1.2.4, launchdarkly-server-sdk-ai-openai 0.7.0, launchdarkly-server-sdk-ai-langchain 0.8.0.
• Smoke-tested the OpenAI example's LD path (client init, completion_config, create_tracker) against a test SDK key with DeprecationWarnings enabled — SDK initialized and produced 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.
• Higher majors exist for launchdarkly-observability (1.2.4) and launchdarkly-server-sdk-ai (1.1.0), but were not adopted for examples whose floor is configured in major 0, to avoid crossing a major boundary. Their open-ended constraints still allow the latest at install time.
• Lock files are gitignored in this repo, so none are committed.

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

---

Note

Low Risk
Dependency-only constraint updates in example projects; no runtime or application logic changes.

Overview
Raises minimum versions for LaunchDarkly AI-related packages in all 10 example pyproject.toml files. There are no application or example source changes—only dependency constraint updates.

Feature examples (create_agent, create_agent_graph, create_model) move launchdarkly-server-sdk-ai from >=1.0.0 to >=1.1.0 (still capped at <2.0.0). Getting started and create_judge bump the core SDK floor from >=0.20.0 to >=0.20.1.

Shared bumps everywhere they appear: launchdarkly-observability >=0.1.0 → >=0.1.1, launchdarkly-server-sdk-ai-openai >=0.5.0 → >=0.7.0, and launchdarkly-server-sdk-ai-langchain >=0.6.0 → >=0.8.0. Existing >= style and major-version caps are unchanged so installs can still resolve newer releases within those bounds.

^{Reviewed by Cursor Bugbot for commit 3a0a092. Bugbot is set up for automated code reviews on this repo. Configure here.}

[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