chore: Update sdk_metadata features

[devin-ai-integration]

Requirements

• I have added test coverage for new or changed functionality
• I have followed the repository's pull request submission guidelines
• I have validated my changes against all supported platform versions

N/A - This is a metadata-only change with no code changes.

Related issues

None

Describe the solution you've provided

This PR adds the features object to .sdk_metadata.json to document all features supported by the Java Server SDK along with the version each feature was introduced.

24 features are documented with their introduction versions, sourced from:

• SDK features documentation table (server-side SDKs A-K table, Java column)
• CHANGELOG.md for features not in the docs table

Feature keys use camelCase names from feature_info.json.

Version sources:

Feature	Version	Source
allFlags	1.0	docs table
appMetadata	5.8	docs table
bigSegments	5.7	docs table
contexts	6.0	docs table
eventCompression	7.9	CHANGELOG
experimentation	5.5	docs table
fileDataSource	4.5	docs table
flagChanges	5.0	docs table
hooks	7.4	docs table
inlineContextCustomEvents	7.8	docs table
migrations	7.0	docs table
offlineMode	1.0	docs table
otel	7.4	docs table
pluginSupport	7.10	CHANGELOG
privateAttrs	2.5	docs table
relayProxyDaemon	1.0	docs table
relayProxyProxy	1.0	docs table
secureMode	1.0	docs table
storingData	1.0	docs table
storingDataRedis	1.0	Redis was built into SDK from v1.0, moved to separate package in v5.0
testDataSource	5.1	docs table
track	1.0	docs table
variationDetail	4.3	docs table
webProxy	2.2	docs table

Describe alternatives you've considered

N/A

Additional context

• Requested by tanderson@launchdarkly.com
• Link to Devin run

Items for reviewer to verify:

• storingDataRedis version (1.0) - Redis was originally built into the SDK and later moved to a separate package
• eventCompression and pluginSupport versions were sourced from CHANGELOG, not the docs table

---

Note

Low Risk
Metadata-only change that should not affect runtime behavior; primary risk is incorrect feature/version entries impacting downstream reporting/docs.

Overview
Adds a features section to .sdk_metadata.json for java-server-sdk, enumerating supported capabilities and the SDK version each was introduced.

Also updates JSON formatting around userAgents (trailing comma) to accommodate the new metadata block.

^{Written by Cursor Bugbot for commit 8ac1927. This will update automatically on new commits. 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 and CI monitoring

[devin-ai-integration]

Version Sources

Feature	Version	Source
allFlags	1.0	docs table
appMetadata	5.8	docs table
bigSegments	5.7	docs table
contexts	6.0	docs table
eventCompression	7.9	CHANGELOG - "Enable gzip option for events in server SDK"
experimentation	5.5	docs table
fileDataSource	4.5	docs table
flagChanges	5.0	docs table
hooks	7.4	docs table
inlineContextCustomEvents	7.8	docs table
migrations	7.0	docs table
offlineMode	1.0	docs table
otel	7.4	docs table
pluginSupport	7.10	CHANGELOG - "Add experimental plugin support"
privateAttrs	2.5	docs table
relayProxyDaemon	1.0	docs table
relayProxyProxy	1.0	docs table
secureMode	1.0	docs table
storingData	1.0	docs table
storingDataRedis	1.0	Redis was built into SDK from v1.0, moved to separate package in v5.0
testDataSource	5.1	docs table
track	1.0	docs table
variationDetail	4.3	docs table
webProxy	2.2	docs table

[devin-ai-integration]

Updated: webProxy version changed from 2.2 to 1.0

After investigating the git history in the java-server-sdk repo, I found that proxy support (proxyHost, proxyPort, proxyScheme methods) was added in v0.10.0 (Aug 7, 2015) and was present in v1.0.1.

The docs table shows 2.2 because that's when proxy authentication (Basic Auth) was added in v2.2.0 (Apr 11, 2017), but basic proxy configuration was available from the beginning.

Updated version source:

Feature	Version	Source
webProxy	1.0	Proxy support added in v0.10.0, present in v1.0.1