[BarMal]

Summary

The latest on-device backfill screenshot shows the strap is now sending historical data (150 history frames, 3 batches, 1 done), but the service still leaves the UI in Connection failed.

This PR fixes the service-level outcome handling for that case.

What changed

• If historical sync throws after rows were persisted, events were persisted, or incoming historical rows were skipped because they already existed, the service now treats the run as a partial success instead of setting WhoopRuntimeState.ERROR.
• Partial-success cleanup still closes the session, enqueues processing for any stored data, marks the sync finished, and stops the foreground service.
• True no-data failures still surface as Connection failed.

Why

The BLE/debug counters prove data can arrive and completion can be observed even when a later cleanup/timeout path throws. In that case, marking the whole run as failed hides the useful result and leaves the debug screen red despite actual historical progress.

Validation

• ./gradlew.bat :app:assembleDebug
• ./gradlew.bat testDebugUnitTest