Upgrade core dependency versions

[zwass]

• crosstool-ng 1.24.0 -> 1.28.0
• LLVM 11.0.0 -> 18.1.8
• GCC 8.3.0 -> 13.4.0
• Linux 4.9.156 -> 4.9.335
• glibc 2.23 -> 2.27 on aarch64, 2.12.2 -> 2.17 on x86_64
• binutils 2.29.1 -> 2.33.1 on aarch64, 2.30.0 -> 2.33.1 on x86_64
• zlib 1.2.13 -> 1.3.1

[zwass]

Will remove libelf, libbpf, and bpftool before re-requesting review.

[Smjert]

Do we need to enable zlib here?

Afaik we compile zlib separately already. Sorry I don't have more guidance right now, but I'm just wondering if we shouldn't just use one or the other, instead of risking having two different versions being used.

[zwass]

@Smjert I dug into this and I think the answer is we should have zlib in both places. Crosstool-ng does seem to require zlib. Maybe in the older version it was implicitly relying on the system zlib?

It seems like we have 2 options for crosstool-ng

1. Use system zlib
2. Build zlib (what this configuration sets)

crosstool-ng does not seem to install or make available this zlib beyond linking it into the generated gcc. Because of that, we also want to build zlib which is required by the LLVM linker.

When I tried removing the explicit zlib build in the script, I found that I would get linker errors later in the build process when the linker could not find the zlib library (preventing the linker from executing).