fix(deps): bump eventsource to v1.11.1

[aaron-zeisler]

Summary

Bumps github.com/launchdarkly/eventsource v1.11.0 → v1.11.1. Supersedes the ld-relay-side workaround in #733.

Background

v1.11.1 fixes a stream-shutdown deadlock (launchdarkly/eventsource#60): when Close raced with an in-flight event, the stream goroutine's discardCurrentStream wedged (it drained its internal errs channel before events while the decoder was blocked sending on events), so stream.Events was never closed and any consumer draining it on shutdown hung forever.

In Relay this hung relay.Close() via the auto-config StreamManager (consumeStream's deferred drain), surfacing as the intermittently-hanging TestAutoConfigAddEnvironmentWithExpiringSDKKeyDoesNotPanicWhenInitFails (panic: test timed out after 10m0s). Fixing eventsource at the root removes the hang with no ld-relay code change, so this replaces the workaround PR #733.

Changes

go.mod / go.sum only.

---

Note

Low Risk
Patch-level dependency update with no ld-relay code changes; risk is limited to eventsource/SSE shutdown behavior, which this release is meant to improve.

Overview
Bumps github.com/launchdarkly/eventsource from v1.11.0 to v1.11.1 (go.mod / go.sum only). No ld-relay application code changes.

v1.11.1 fixes a stream-shutdown deadlock when Close races with an in-flight event: the stream goroutine could wedge and never close stream.Events, so shutdown paths that drain that channel (e.g. auto-config StreamManager / consumeStream, and thus relay.Close()) could hang indefinitely. That behavior showed up as intermittent test timeouts such as TestAutoConfigAddEnvironmentWithExpiringSDKKeyDoesNotPanicWhenInitFails. This dependency bump is intended to fix the issue at the library root and supersede an ld-relay workaround (PR #733).

^{Reviewed by Cursor Bugbot for commit 45acf95. Bugbot is set up for automated code reviews on this repo. Configure here.}