Remove zlib dependencies from eng/common/native/install-dependencies.sh

[carlossanlop]

Fixes dotnet/runtime#105373
Follow up of dotnet/runtime#111939

[carlossanlop]

Nothing broke but I think I should go back to draft and first test this change in a test PR in the runtime repo, just in case any CI leg fails.

[jkoritzinsky]

I think to truly validate this, you need to build the docker images with the updates build-rootfs script and make sure that we can still build all branches we're still servicing with the new images.

[am11]

Nothing broke but I think I should go back to draft and first test this change in a test PR in the runtime repo, just in case any CI leg fails.

This script is not used in CI by arcade and runtime repos. It's used by https://github.com/dotnet/dotnet-buildtools-prereqs-docker and it's used for older versions of prereq containers from the main branch as well (servicing branches). Testing is done in multiple steps (build prereq image, then use that container image to build runtime), usually in local machine.

[carlossanlop]

This script is not used in CI by arcade and runtime repos.

Alright. But can I still assume that the change needs to be made here in arcade? @am11

I don't know how the code flows from between arcade and the prereqs repo.

[am11]

@carlossanlop, I think there are two opposing thought processes:

1. we want to keep non-portable build support in rootfs: for that reason we are still carrying libunwind dependency in rootfs script although it was removed in .NET Core 2.1 in favor of local copy dotnet/coreclr@d104270. By this logic, this PR should "replace" zlib with zlib-ng.
2. we don't want non-portable build support in rootfs: by this logic, we should also remove libunwind.

[jkotas]

@carlossanlop There is a conversation about this on Teams (Build Tools Prereqs V-Team)

[carlossanlop]

Closing as the changes are more complex than just this.

[jkotas]

@carlossanlop Can we keep the cleanup in install-dependencies.sh? I do not think that install-dependencies.sh suffers from the problematic use in the prereqs repo.

[carlossanlop]

Sure.

[jkotas]

Thanks!