chore: update launchdarkly-openfeature-server to 0.5.1

[devin-ai-integration]

Summary

Bumps the launchdarkly-openfeature-server dependency constraint in pyproject.toml from ^0.5.0 to ^0.5.1, the latest published release on PyPI (same major, floor raised not lowered, caret pin style preserved).

- launchdarkly-openfeature-server = "^0.5.0"
+ launchdarkly-openfeature-server = "^0.5.1"

Pulls in launchdarkly-server-sdk 9.14.1 and openfeature-sdk 0.8.4 transitively.

Validation

• poetry install succeeds (resolves launchdarkly-openfeature-server 0.5.1).
• poetry run python main.py runs against a real SDK key and evaluates a flag successfully (*** The sample-feature feature flag evaluates to False.).
• No deprecated SDK/OpenFeature APIs in main.py — uses standard api.set_provider / api.get_client / get_boolean_value / EvaluationContext.

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

---

Note

Low Risk
Single-line dependency floor bump in a sample app with no code changes; low blast radius.

Overview
Raises the Poetry dependency on launchdarkly-openfeature-server from ^0.5.0 to ^0.5.1 in pyproject.toml. No application or workflow changes; main.py and CI stay the same.

Lock resolution picks up newer transitive versions (e.g. launchdarkly-server-sdk and openfeature-sdk) as described in the PR notes.

^{Reviewed by Cursor Bugbot for commit 01b7a91. 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

[devin-ai-integration]

Closing: no update needed. The existing constraint launchdarkly-openfeature-server = "^0.5.0" (i.e. >=0.5.0,<0.6.0) already permits the latest release 0.5.1, so bumping to ^0.5.1 changes nothing functional. Per the maintenance policy, updates already satisfied by the existing constraint are dropped.