fix: add proper exception handling for background event source

[suthar26]

• adds explicit exception handling which was causing app crashes due to a race condition

[Copilot]

Pull Request Overview

Adds a safety wrapper around BackgroundEventSource to prevent crashes caused by RejectedExecutionException during start/close lifecycle. Key changes include introducing SafeBackgroundEventSource with guarded start/close methods and updating DevCycleClient to use the new wrapper.

• Introduces SafeBackgroundEventSource with explicit exception handling
• Replaces direct BackgroundEventSource usage in DevCycleClient with the safe wrapper

Reviewed Changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
SafeBackgroundEventSource.kt	New wrapper adds guarded start/close to avoid executor rejection crashes
DevCycleClient.kt	Replaces raw BackgroundEventSource with SafeBackgroundEventSource to apply safer lifecycle management

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[jsalaber]

https://www.javadoc.io/doc/com.launchdarkly/okhttp-eventsource/latest/com/launchdarkly/eventsource/EventSource.Builder.html

I'm wondering if we can also make use of the options in the EventSource to always continue instead of throwing an exception

[Copilot]

Pull Request Overview

Copilot reviewed 1 out of 1 changed files in this pull request and generated 1 comment.

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[Copilot]

Using ErrorStrategy.alwaysContinue() silently suppresses all errors, which could mask critical issues and make debugging difficult. Consider implementing a custom error strategy that logs errors before continuing, or use a strategy that retries with backoff for transient errors while failing fast for non-recoverable ones.

Suggested change

	).errorStrategy(ErrorStrategy.alwaysContinue())
	).errorStrategy { error, _ ->
	DevCycleLogger.e("EventSource error: ${error.message}", error)
	ErrorStrategy.Action.CONTINUE
	}