Bump submodules: HealthKit glucose purge fix, Support build info

[ps2]

Glucose readings no longer deleted from Apple Health

Loop deletes its own glucose readings from Health once the Dexcom app should have written its copies. In G7 direct mode, or whenever the Dexcom app wasn't writing, nothing replaced them, and Health kept only the last 3 hours from Loop.

• Only let Loop purge its HealthKit glucose while eavesdropping G7SensorKit#95: no purge in G7 direct mode
• Only purge HealthKit glucose that another app has written LoopKit#651: only readings that another app has already written are deleted
• Refresh the managed HealthKit interval on CGM status updates Loop#2584: a change of G7 mode takes effect without relaunching

Support section shows build info

• Show branch, revision, customizations and launch time in Support Loop#2583: Branch, Revision, Customizations (.loopcustomization files), launch time and time since launch under Settings → Support

Store from a newer model

• Refuse a store from a newer model LoopKit#650 made PersistenceController refuse a store written by a newer model. That turned out to be unnecessary and harmful: Core Data keeps the store's model in the store, so an older build migrates a newer store down and keeps the shared data. That is how going from next-dev back to dev already works. Revert the newer-store guard from #650 LoopKit#652 reverts it.

Submodules: G7SensorKit → e17129d, Loop → 859b61d7, LoopKit → abea6bc2, each at its next-dev tip. Everything else is unchanged.

Tested: full LoopWorkspace scheme simulator build at these pins, with all 19 plugins bundled.