Asia/Tehran format should not use 'J'

[nayarsystems]

Asia/Tehran format should not use 'J'

[jaracil]

The POSIX TZ strings are obtained from /usr/share/zoneinfo directory in Arch Linux system.
We can't patch individual strings from .json and .csv files, because they are autogenerated every time there is a new time-zone update.

[Docteh]

@Diramu as an outside observer I'm noticing that the timezone for Asia/Tehran is now <+0330>-3:30<+0430>,J79/24,J263/24

Personally I'm using Ubuntu, which has Debian as upstream, https://packages.debian.org/sid/tzdata
https://www.iana.org/time-zones

snippet from the asia file

Rule	Iran	2000	only	-	Mar	20	24:00	1:00	-
Rule	Iran	2000	only	-	Sep	20	24:00	0	-
Rule	Iran	2001	2003	-	Mar	21	24:00	1:00	-
Rule	Iran	2001	2003	-	Sep	21	24:00	0	-
Rule	Iran	2004	only	-	Mar	20	24:00	1:00	-
Rule	Iran	2004	only	-	Sep	20	24:00	0	-
Rule	Iran	2005	only	-	Mar	21	24:00	1:00	-
Rule	Iran	2005	only	-	Sep	21	24:00	0	-
Rule	Iran	2008	only	-	Mar	20	24:00	1:00	-
Rule	Iran	2008	only	-	Sep	20	24:00	0	-
Rule	Iran	2009	2011	-	Mar	21	24:00	1:00	-
Rule	Iran	2009	2011	-	Sep	21	24:00	0	-
Rule	Iran	2012	only	-	Mar	20	24:00	1:00	-
Rule	Iran	2012	only	-	Sep	20	24:00	0	-
Rule	Iran	2013	2015	-	Mar	21	24:00	1:00	-
Rule	Iran	2013	2015	-	Sep	21	24:00	0	-
Rule	Iran	2016	only	-	Mar	20	24:00	1:00	-
Rule	Iran	2016	only	-	Sep	20	24:00	0	-
Rule	Iran	2017	2019	-	Mar	21	24:00	1:00	-
Rule	Iran	2017	2019	-	Sep	21	24:00	0	-
Rule	Iran	2020	only	-	Mar	20	24:00	1:00	-
Rule	Iran	2020	only	-	Sep	20	24:00	0	-
Rule	Iran	2021	2023	-	Mar	21	24:00	1:00	-
Rule	Iran	2021	2023	-	Sep	21	24:00	0	-
Rule	Iran	2024	only	-	Mar	20	24:00	1:00	-
Rule	Iran	2024	only	-	Sep	20	24:00	0	-

They appear to be hard coding every leap year. Looks like the older POSIX TZ variables are better at handling leap years than the more modern IANA data.