Update tzdata / leap-second file with June 2024 expiry

Brief Description
-----------------
The current tzdata / leap-second files have an expiry of Dec 28, 2023. This launchpad tracks updating to a newer version of the files w/ expiry of Jun 2024.

Note: The leap-second file was previously updated as part:
- https://bugs.launchpad.net/starlingx/+bug/2015272
- https://bugs.launchpad.net/starlingx/+bug/1995645

Leap second announcement: https://datacenter.iers.org/data/latestVersion/16_BULLETIN_C16.txt

At this time, there is no new tzdata package that includes an updated leap-second file, so the proposal is to patch the existing file.

Severity
--------
Major - ptp functionality doesn't work if the leap-second files expire as per CGTS-36305

Steps to Reproduce
------------------
N/A

Expected Behavior
-----------------
N/A

Actual Behavior
---------------
N/A

Reproducibility
---------------
N/A

System Configuration
--------------------
Any

Load info (eg: 2022-03-10_20-00-07)
-----------------------------------
Affects the main branch as well as stx.8.0 & stx.7.0

Last Pass
---------
N/A

Timestamp/Logs
--------------
N/A

Alarms
------
N/A

Test Activity
-------------
Monitoring of leap-second file expiry

Workaround
----------
copy a new leapseconds.list file on the controller

$ cat /home/sysadmin/leapseconds.list | grep expire
# File expires on: 28 June 2024

$ system ptp-instance-parameter-add ts1 leapfile=/home/sysadmin/leapseconds.list

$ system ptp-instance-apply
Applying the PTP Instance configuration

$ system ptp-instance-show ts1
| parameters | [u'logging_level=7', u'domainNumber=24', u'ts2phc.nmea_serialport=/dev/ttyGNSS_5100_0', u'use_syslog=1', u'leapfile=/home/sysadmin/leapseconds.list', u'slaveOnly=0'] |

$ cat /usr/share/zoneinfo/leap-seconds.list | grep expire
# File expires on: 28 June 2024

$ cat /usr/share/zoneinfo/leapseconds | grep expire
# UTC timestamp when this leap second list expires.
#expires 1672185600 (2022-12-28 00:00:00 UTC)
# File expires on: 28 June 2024