Update tz db to 2015d

Update tz db to 2015d

  Egypt will not observe DST in 2015.

  See http://mm.icann.org/pipermail/tz-announce/2015-April/000031.html
  and http://en.wikipedia.org/wiki/Egypt_Standard_Time

BUG=473288
TBR=mark@chromium.org,jsbell@chromium.org
TEST=In JS console, run the following to get 1:00 PM for 2015
instead of 2:00 PM. In 2014, it should return 2:00 PM.
  may_25_2015_1100 = new Date("05/25/2015 11:00Z")
  may_25_2015_1100.toLocaleString("en", {timeZone: "Africa/Cairo"})
  may_25_2014_1100 = new Date("05/25/2014 11:00Z")
  may_25_2014_1100.toLocaleString("en", {timeZone: "Africa/Cairo"})

Committed: https://chromium.googlesource.com/chromium/deps/icu/+/5788e2736b3bc642994b6351a6096124895afa01

[jungshik at Google, 2015-05-12 19:31:03]

jshin@chromium.org changed reviewers:
+ jsbell@chromium.org

[jsbell, 2015-05-12 22:23:36]

Can you split this in two?

The tz db update seems obvious (and we should land that asap).

The EUC-KR update seems like we should not add the new code point if it's just
going to be a compatibility issue.

[jungshik at Google, 2015-05-15 19:22:12]

On 2015/05/12 22:23:36, jsbell wrote:
> Can you split this in two?
> 
> The tz db update seems obvious (and we should land that asap).
> 
> The EUC-KR update seems like we should not add the new code point if it's just
> going to be a compatibility issue.

Yeah... I'll.

[jungshik at Google, 2015-05-15 20:07:30]

Committed patchset #2 (id:10001) manually as
5788e2736b3bc642994b6351a6096124895afa01 (presubmit successful).