chore: Fix segment key in FileData example (includes → included)

[devin-ai-integration]

Summary

What: The JSON segment example in the file data source Javadoc (FileData.java) used "includes" for segment members. Changed it to "included".

Why: The canonical segment field is "included" (with "excluded"). The parser reads included, so an includes key is silently dropped and copy-pasting the example doesn't actually add members to the segment.

Change:

 "segments": {
   "segment-key-1": {
     "key": "segment-key-1",
-    "includes": [ "user-key-1" ]
+    "included": [ "user-key-1" ]
   }
 }

Docs-only comment fix. No code, CHANGELOG, or version changes. Mirrors ruby-server-sdk#406 and sdk-meta#541.

Link to Devin session: https://app.devin.ai/sessions/741446729be24f46bb034334384575c7
Requested by: @jsonbailey

---

Note

Low Risk
Comment-only Javadoc change with no runtime, API, or behavioral impact.

Overview
Corrects the file data source Javadoc sample in FileData.java so segment membership uses included instead of includes, matching what the file parser and LaunchDarkly segment JSON actually expect.

Copy-pasting the old example would leave segment members ignored because includes is not a recognized field; the doc now aligns with included / excluded usage elsewhere in the SDK.

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