chore: update Gemfile.lock transitive gems to latest

[devin-ai-integration]

Summary

Refreshes the committed Gemfile.lock so a fresh bundle install for the CocoaPods toolchain resolves the same versions that are current on RubyGems.

• activesupport 7.2.3.1 → 7.2.3.2, concurrent-ruby 1.3.7 → 1.3.8, json 2.21.1 → 2.21.2 (transitive only; cocoapods (~> 1.17.0) stays at 1.17.0, which is latest).
• No LaunchDarkly SDK change: pod 'LaunchDarkly', '>= 11.2' with no committed Podfile.lock already resolves to the latest 11.x, verified as 11.6.0.
• No deprecated SDK APIs in the example: the only deprecations in ios-client-sdk 11.6.0 are LDClient.start(config:context:completion:) (the example already uses the startWaitSeconds: overload) and identify with optional completion, which the example does not call.
• BUNDLED WITH intentionally left at 2.0.1 to keep the diff scoped.

Implementation details

Regenerated with bundle lock --update (Ruby 3.4 container), then reverted the incidental BUNDLED WITH rewrite.

Verification:

• pod install run on Linux (CocoaPods 1.17.0 from this lockfile) resolved LaunchDarkly 11.6.0 + LDSwiftEventSource 3.3.0 and integrated the workspace successfully — confirming the existing Podfile constraint already picks up the newest SDK, so no version bump is warranted (bumping the floor to >= 11.6 would change nothing; the same reasoning closed chore: update LaunchDarkly iOS SDK to 11.3 #71).
• The example cannot be built or run here: Xcode/macOS is unavailable on Linux, so the iOS/watchOS build relies on the repo's own macos-build CI job. The mobile key was exercised out-of-band against clientsdk.launchdarkly.com to confirm flag delivery works for the hello-apps environment.
• SDK deprecation check done by grepping @available(*, deprecated in ios-client-sdk at tag 11.6.0.

Link to Devin session: https://app.devin.ai/sessions/818e0a367b90429eb4ee9bad9b5b64f4
Open in Devin Desktop: https://app.devin.ai/desktop/session/818e0a367b90429eb4ee9bad9b5b64f4?variant=devin

[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]

@cursor review