Daily analytics summary, settings state and device models

[ps2]

Backport of #2574, #2578 and #2582 from next-dev. dev's code had diverged, so this is a hand port in one commit rather than cherry-picks.

• Daily summary: one "Daily summary" event per local day replaces the per-cycle "Loop success", "Loop error" and "CGM Fetch" events. It has loop success count and mean/max duration, loop error counts by issue id, the count of stored CGM readings, the day's UTC offset and the settings state.
• Settings state: closed loop, dosing strategy, integral retrospective correction and glucose based partial application are sent as user properties at launch and when they change, with "Closed loop enabled change", "Dosing strategy change" and "Algorithm experiment change" events.
• Devices: Pump Type/CGM Type and Pump Model/CGM Model user properties are sent at launch and setup, when a status update reports a different model, and as "None" on removal.
• No health data: bolus units, carb grams, preset names, targets and sensitivity are no longer sent. Override events carry the kind and duration, and "Override Ended" is now sent.
• Alerts: "Alert Displayed" replaces "Alert Issued". Immediate alerts are reported when issued, delayed and repeating alerts once they come due without being retracted (checked after each loop), and loop-not-running notifications when Loop infers their delivery.
• "Settings Screen" is sent when Settings opens. Carb and bolus events from the phone are in session; watch and remote ones stay out of session.

Differences from next-dev

• dev's glucose samples don't record backfill, so the summary has glucoseCount but no backfillCount or maxBackfillAgeMinutes.
• dev reports loops and CGM readings from background queues, so the summary and state are updated on the main queue instead of being @MainActor.
• dev has no activity presets, so override events have no activity type, and the legacy workout override is reported with kind "workout".

Testing

• The LoopWorkspace scheme builds for the iOS Simulator. All 306 LoopTests pass, including testLookupScheduledAlertsDue, ported from next-dev.
• In the simulator, the stored summary had the right counts and settings state. Toggling integral retrospective correction logged "Algorithm experiment change" and re-sent the user properties.
• A temporary test, not included here, checked the day rollover. A summary dated yesterday was sent as "Daily summary" with its counts and replaced by today's, and a changed experiment produced the change event and updated user property.

[marionbarker]

I rely on others for code review.
✅ successful build using Xcode 27 onto iOS 27.0.1 SE 3rd gen phone
❓ successful test local clone to iOS 26.5 simulator
❓ successful test local clone to iOS 27 simulator

Sometimes this test failed. Other times it did not.
testRescheduleMutedLoopNotLoopingAlerts

Failure was on the XCTAssertNil for line 509 of LoopTests/Managers/Alerts/AlertManagerTests.swift.

[ps2]

Thanks for testing, Marion. The intermittent testRescheduleMutedLoopNotLoopingAlerts failure isn't from this PR. The test is the same on dev, and nothing here changes it or the notification scheduling it checks.

It uses the simulator's real notification center, and it reads the pending notifications once, without waiting for the muted versions to replace the unmuted ones. When the simulator has been idle for a while, the notification service is slow on the first run, so the test can read the list too early and fail. It usually passes on later runs. I'll open a separate PR to make the test wait for the muted notifications.

[marionbarker]

Approve since intermittent test issue will be solved in a different PR.