DO NOT MERGE: Fix serious DST issue with non-DST time zones

* When finding a match for an EAS time zone without DST, we were
  checking the offset, but NOT the DST status; therefore, we could
  match the wrong time zone (depending on the order of items in the
  TZ database)
* All users with events set up in non-DST timezones would have their
  events show up at the wrong time after a DST transition
* The fix is to first check against the default time zone, and use
  that if it's a match; otherwise, to use the first time zone that
  matches both offset and DST availability

Backport from master

Bug: 4337360
Change-Id: Id7992095551e59efe449651b39f5cd7bc3a9f9d8
2 files changed