chore: replace workspace:^ with static versions in example apps

[joker23]

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

No test changes needed — this only affects example app dependency declarations and release-please configuration.

Related issues

SDK-2157

Describe the solution you've provided

Replaces all workspace:^ references for @launchdarkly/* dependencies in example app package.json files with their current static versions from .release-please-manifest.json (or the package's own package.json for electron/svelte which are not yet in the manifest).

Adds extra-files entries to release-please-config.json so these versions are automatically bumped on future releases.

Affected example apps (12 files):

• packages/sdk/browser/example and example-fdv2 → @launchdarkly/js-client-sdk 4.4.1
• packages/sdk/electron/example → @launchdarkly/electron-client-sdk 0.0.1
• packages/sdk/react-native/example → @launchdarkly/react-native-client-sdk 10.15.1
• packages/sdk/svelte/example → @launchdarkly/svelte-client-sdk 0.1.0
• 7 server-ai examples (openai, bedrock, vercel-ai, tracked-chat, chat-judge, direct-judge, chat-observability) → static versions for node-server-sdk, server-sdk-ai, and the relevant AI provider packages

release-please-config.json changes:

• Added extra-files to existing entries: browser, react-native, server-node, server-ai, server-ai-openai, server-ai-vercel, server-ai-langchain
• Added new entries for packages/sdk/electron and packages/sdk/svelte (not yet in the release-please manifest — entries will take effect once those packages join the release pipeline)
• Cross-package references (e.g., server-ai examples depending on node-server-sdk) use absolute paths from repo root, following the existing server-node → react-server-example pattern

Describe alternatives you've considered

N/A — this follows the established pattern already used by cloudflare, fastly, akamai-base, akamai-edgekv, and react example apps.

Additional context

Human review checklist

• Verify the static versions match current published versions (sourced from .release-please-manifest.json)
• Confirm extra-files jsonpath expressions match the actual dependency key names in each example's package.json
• Confirm that adding packages/sdk/electron and packages/sdk/svelte to release-please-config.json won't cause issues before those packages are added to the manifest
• Verify cross-package extra-files use absolute paths (/packages/...) while same-package entries use relative paths

Link to Devin session: https://app.devin.ai/sessions/c56e3cf1d5e84389a79b9e3f818605c4
Requested by: @joker23

---

Note

Low Risk
Low risk since changes are limited to example-app dependency version pinning and release-please config updates; main risk is misconfigured jsonpath/paths causing future automated bumps to miss or update the wrong fields.

Overview
Pins previously workspace:^ LaunchDarkly dependencies in multiple example apps (browser, Electron, React Native, Svelte, and several server-ai examples) to specific published versions.

Updates release-please-config.json to add extra-files entries (and new package sections for packages/sdk/electron and packages/sdk/svelte) so future releases automatically bump the corresponding dependency versions in these example package.json files, including cross-package references like @launchdarkly/node-server-sdk used by the server-ai examples.

^{Reviewed by Cursor Bugbot for commit dfac6c5. 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 and CI monitoring

[devin-ai-integration]

@cursor review

[github-actions]

@launchdarkly/js-sdk-common size report
This is the brotli compressed size of the ESM build.
Compressed size: 25661 bytes
Compressed size limit: 29000
Uncompressed size: 126143 bytes

[github-actions]

@launchdarkly/browser size report
This is the brotli compressed size of the ESM build.
Compressed size: 179348 bytes
Compressed size limit: 200000
Uncompressed size: 830127 bytes

[github-actions]

@launchdarkly/js-client-sdk size report
This is the brotli compressed size of the ESM build.
Compressed size: 31736 bytes
Compressed size limit: 34000
Uncompressed size: 112937 bytes

[github-actions]

@launchdarkly/js-client-sdk-common size report
This is the brotli compressed size of the ESM build.
Compressed size: 37181 bytes
Compressed size limit: 38000
Uncompressed size: 204409 bytes

[joker23]

@cursor review

[cursor]

✅ Bugbot reviewed your changes and found no new issues!

Comment @cursor review or bugbot run to trigger another review on this PR

^{Reviewed by Cursor Bugbot for commit 1e5d2f0. Configure here.}