8294357: (tz) Update Timezone Data to 2022d

[satoyoshiki]

Please review this PR. This MR is a clean backprot of JDK-8294357: (tz) Update Timezone Data to 2022d

---

Progress

• Change must not contain extraneous whitespace
• Commit message must refer to an issue

Issue

• JDK-8294357: (tz) Update Timezone Data to 2022d

Reviewing

Using git

Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk19u pull/45/head:pull/45
$ git checkout pull/45

Update a local copy of the PR:
$ git checkout pull/45
$ git pull https://git.openjdk.org/jdk19u pull/45/head

Using Skara CLI tools

Checkout this PR locally:
$ git pr checkout 45

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

Using diff file

Download this PR as a diff file:
https://git.openjdk.org/jdk19u/pull/45.diff

[bridgekeeper]

👋 Welcome back ysatowse! 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.

[openjdk]

@satoyoshiki This change now passes all automated pre-integration checks.

ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details.

After integration, the commit message for the final commit will be:

8294357: (tz) Update Timezone Data to 2022d

You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed.

At the time when this comment was updated there had been 2 new commits pushed to the master branch:

• e2a9916: 8292969: Bad Thread Utilization in ForkJoinPool
• 1454bf2: 8291633: Build failures with GCC 11, Alpine 3 due to incompatible casts from nullptr

Please see this link for an up-to-date comparison between the source branch of this pull request and the master branch.
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details.

As you do not have Committer status in this project an existing Committer must agree to sponsor your change.

➡️ To flag this PR as ready for integration with the above commit message, type /integrate in a new comment. (Afterwards, your sponsor types /sponsor in a new comment to perform the integration).

[satoyoshiki]

/integrate

[openjdk]

@satoyoshiki
Your change (at version 509876b) is now ready to be sponsored by a Committer.

[mlbridge]

Webrevs

• 00: Full (509876b1)

[naotoj]

/sponsor

[openjdk]

Going to push as commit 689f8f2.
Since your change was applied there have been 2 commits pushed to the master branch:

• e2a9916: 8292969: Bad Thread Utilization in ForkJoinPool
• 1454bf2: 8291633: Build failures with GCC 11, Alpine 3 due to incompatible casts from nullptr

Your commit was automatically rebased without conflicts.

[openjdk]

@naotoj @satoyoshiki Pushed as commit 689f8f2.

💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored.