Changes

fix readline multilib dependencies for 64bit

avoid dpkg-cross failing on packages that we don't use

drop sparc patch #1034779 applied in pcre2 #10.42-2

fix pam FTBFS #1054228

drop bogus pam FTBFS patch #1054228

The patch actually causes no patches to be applied. pam has been fixed
by other means in the mean time.

debhelper also truncates NEWS now - causing differences

fix /usr-merge induced e2fsprogs FTBFS #1053111

fix dash FTCBFS #1057339

fix icu FTCBFS #1057726

fix pam FTCBFS #1057729

work around elf-arch only recognizing some mips64r6el binaries

drop loong64 patch #1024359 applied in libffi/3.4.4-2

drop loong64 patch #1031850 resolved in gcc-13

adapt to linux-libc-dev having become a:all+m-a:foreign

Most of the time, we no longer have to rebuild linux-libc-dev.
Sometimes, it's missing headers though and then we need to rebuild it,
but not as a cross build, but an indep-only build.

linux: circumvent control generation protection more reliably

reenable building of gcc-13 common libraries

gcc-14 entered unstable.

adapt linux patching to toml based configuration

rewrite wdotap patch set on top of gcc-for-host changes

The merging of gcc-for-host caused a lot of changes to the gcc packaging
and made the wdotap patch set from cross-gcc-dev no longer work. It
required significant changes and quite some aspects could be dropped
resulting in a much smaller patch that is inlined in rebootstrap for
now. We'll see whether that works better or worse.

don't attempt to install linux-libc-dev with an :arch qualifier

enable wdotap patch for gcc-14

linux: always regenerate d/control

Since linux-libc-dev is arch:all now, we only have two cases. Either the
one in the archive is good enough or we get to build it. When we build
it, we bump the version. When we bump the version, we must regenerate
d/control (changed in src:linux).

gcc: move -for-host packages from cross toolchain to rtlibs build #1069065

new linux d/control dependency python3-dacite