GLIBC patching and linker improvements

[gcurtis]

Umbrella issue that tracks improvements to GLIBC patching.

- [ ] https://github.com/jetpack-io/devbox/issues/1854
- [ ] https://github.com/jetpack-io/devbox/issues/1855
- [ ] https://github.com/jetpack-io/devbox/issues/1856
- [ ] https://github.com/jetpack-io/devbox/issues/1798
- [ ] https://github.com/jetpack-io/devbox/issues/1857

[abbudao]

I just stumbled on GLIBC issues with my current DevBox usage, and I'm unsure if this umbrella issue covers my use case. Would you be willing to chime in and give me some insight if that's the case? I could also start a new issue if that's desirable.

I'm doing a POC for my company where we are testing Devbox for local development and CI, but we need to deploy by building Docker Images on CI and moving the compiled static to the container. But we face version mismatches between the compiled and the container image GLIBC. For context, it is a Rust application.

I'm no Nix expert, so I have no idea of the feasibility of this, but it would be great if I could specify the targeted glibc version on devbox.json, and everything would just work as intended. Currently adding glibc pinned to a version breaks Devbox itself.