8292579: (tz) Update Timezone Data to 2022c

[alvdavi]

Backport of tzdata 2022c to jdk8u using the rearguard data for JDK8

---

Progress

• Change must be properly reviewed (1 review required, with at least 1 Reviewer)
• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8292579: (tz) Update Timezone Data to 2022c

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk8u-dev pull/119/head:pull/119
$ git checkout pull/119

Update a local copy of the PR:
$ git checkout pull/119
$ git pull https://git.openjdk.org/jdk8u-dev pull/119/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 119

View PR using the GUI difftool:
$ git pr show -t 119

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk8u-dev/pull/119.diff

[bridgekeeper]

👋 Welcome back alvdavi! A progress list of the required criteria for merging this PR into master will be added to the body of your pull request. There are additional pull request commands available for use with this pull request.

[openjdk]

This backport pull request has now been updated with issue from the original commit.

[mlbridge]

Webrevs

• 00: Full (65800eca)

[jerboaa]

@alvdavi @gnu-andrew We should probably try to get this into jdk8u as a critical fix for October. If so, re-create the PR in https://github.com/openjdk/jdk8u. Thoughts? Please also be sure to have this in JDK 11 and JDK 17. Thanks!

[gnu-andrew]

This is quite a disruptive update due to changes in 2022b. While we need the timezone changes, I'll have to look at how those changes were handled in trunk. Last I checked, this was still being debated there.

[gnu-andrew]

One thing I don't immediately see is a new translation key to handle Europe/Kyiv. We had to patch that locally when using 2022b&c.

[jerboaa]

@alvdavi Please close this one as it's been fixed with openjdk/jdk8u#19 and will come to jdk8u-dev with a merge from jdk8u. Thanks!