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

[devin-ai-integration]

Summary

What: The JSON segment example in the file data source docs used "includes" for segment members. Changed it to "included" in both ldfiledata/package_info.go and ldfiledatav2/package_info.go.

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 documentation changes with no runtime or API impact.

Overview
Corrects the file data source package docs so the sample segment object uses "included" instead of "includes" for member user keys.

The same comment-only fix is applied in ldfiledata and ldfiledatav2 package_info.go JSON examples. Copy-pasted configs now match what the parser expects (included / excluded), so segment members are not silently ignored.

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