time64.inc: clean up and add upstream tickets where issues remain

A number of items are removed because the issues have been resolved
with recipe patches (in separate commits).

Some issues were resolved via upstream version updates that bring in
needed fixes:

glib-2.0 update to 2.78.0 that includes:
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3547
https://gitlab.gnome.org/GNOME/glib/-/merge_requests/3550

curl update to 8.3.0 that includes
curl/curl#11610

util-linux update to 2.39 that includes
util-linux/util-linux#2430
util-linux/util-linux@3ab9e69
util-linux/util-linux#2435

glib-networking update to 2.78.0 that includes
https://gitlab.gnome.org/GNOME/glib-networking/-/merge_requests/241

python3-cryptography update to 42.0.0 which resolves
pyca/cryptography#9370 via
pyca/cryptography#9964

perl update to 5.40.0 which includes
Perl/perl5#21379

python3 update to 3.13.0 which includes
python/cpython#118425
python3 update to 3.13.1 which includes
python/cpython#124972

tcl update to 9.0.0 which includes
tcltk/tcl@4ca6172
(tcl8 recipe has a simple backport of this)

dbus update to 1.16.0 which includes
https://gitlab.freedesktop.org/dbus/dbus/-/merge_requests/444
https://gitlab.freedesktop.org/dbus/dbus/-/merge_requests/289

openssh update to 10.0p1 which includes
openssh/openssh-portable#425
https://bugzilla.mindrot.org/show_bug.cgi?id=3684
https://marc.info/?l=openbsd-bugs&m=172561736524815&w=2
https://lists.mindrot.org/pipermail/openssh-unix-dev/2024-October/041621.html
(all reporting the same issue)

gcc update to 15.1 which includes
llvm/llvm-project#99699
via gcc-mirror/gcc@fa32100
and allows dropping special flags and exceptions for gcc-sanitizers.

Signed-off-by: Alexander Kanavin <alex@linutronix.de>

Author: kanavin

meta/conf/distro/include/time64.inc

@@ -2,11 +2,19 @@
 # QB_OPT_APPEND:append = " -rtc base=2040-02-02"
 #
 # Note that this does result in ptest failures on qemux86:
-# perl python3 dbus openssl glibc-tests openssh curl glib-2.0 tcl libmodule-build-perl
-# and a subset of those occurs in qemux86-64 as well:
-# curl python3 openssl openssl tcl python3-cryptography
+#
+# (none known at this point)
+#
+# and some ptest failures appear in qemux86-64 as well:
+#
+# openssl https://github.com/openssl/openssl/issues/21671
 #
 # Working to address those (before Y2038 rolls in) will be appreciated.
+#
+# Note: some issues occur on 32 bit regardless of the date set:
+#
+# lttng-tools ptest is not going to pass on 32 bit in any case until 2.14.x is released
+#
 
 GLIBC_64BIT_TIME_FLAGS = "${GLIBC_64BIT_TIME_FLAGS_WHEN_NEEDED}"
 
@@ -25,12 +33,8 @@ GLIBC_64BIT_TIME_FLAGS:pn-glibc-testsuite = ""
 # both 32 and 64 bit file APIs.  But it does not handle the time side?
 # Needs further investigation
 GLIBC_64BIT_TIME_FLAGS:pn-pipewire = ""
-# Undefines _FILE_OFFSET_BITS on purpose in
-# libsanitizer/sanitizer_common/sanitizer_platform_limits_posix.cpp
-GLIBC_64BIT_TIME_FLAGS:pn-gcc-sanitizers = ""
 
 # Caused by the flags exceptions above
-INSANE_SKIP:append:pn-gcc-sanitizers = " 32bit-time"
 INSANE_SKIP:append:pn-glibc = " 32bit-time"
 
 # Strace has tests that call 32 bit API directly, which is fair enough, e.g.