Update tzdata to 2022b

[albertyw]

Version

v12 and up

Platform

All platforms

Subsystem

icu-small

What steps will reproduce the bug?

$ node
Welcome to Node.js v18.7.0.
Type ".help" for more information.
> const data = new Date(Date.UTC(2022, 8, 6, 12));
undefined
> new Intl.DateTimeFormat('en-US', {timeZone: 'Europe/Kiev'}).format(data)
'10/5/2022'

> new Intl.DateTimeFormat('en-US', {timeZone: 'Europe/Kyiv'}).format(data)
Uncaught RangeError: Invalid time zone specified: Europe/Kyiv
    at new DateTimeFormat (<anonymous>)
# Should Resolve the same as Europe/Kiev

> new Intl.DateTimeFormat('en-US', {timeZone: 'America/Santiago', timeZoneName: ['shortOffset']}).format(data)
'9/6/2022, GMT-3'
# Should be GMT-4

How often does it reproduce? Is there a required condition?

This is reproducible on all version of node with a dependency on icu-small.

What is the expected behavior?

See changes from tzdata 2022b in http://mm.icann.org/pipermail/tz-announce/2022-August/000071.html

Note that tzdata 2022c has also been released (http://mm.icann.org/pipermail/tz-announce/2022-August/000072.html) but contains less substantive changes.

What do you see instead?

Incorrect future timezone conversions for Chile, Ukraine, and Iran.

Additional information

PR in progress.

[VoltrexKeyva]

Updated by f59d8d3.