Bring in Tidepool LoopAlgorithm updates

The binary-search filterDateRange overload assumes its collection is sorted
ascending by startDate, but returns silently-wrong results otherwise. Add a
debug-only assert enforcing that contract (compiled out of release builds, so
no runtime cost).

This immediately surfaced an existing violation: testGlucoseEffectFromHistory
built a `basal` schedule with segments out of order (and one with endDate
before startDate, plus overlaps). Replace it with a well-formed sorted,
contiguous, non-overlapping schedule, and regenerate the expected-effect
fixture to match the corrected schedule.

Assert filterDateRange input is sorted ascending