llvm-config.exe reports zstd.dll.lib which does not exist on conda-forge

### Solution to issue cannot be found in the documentation.

- [x] I checked the documentation.

### Issue

@JarrettSJohnson reported in https://github.com/conda-forge/mesalib-feedstock/pull/108#discussion_r2009214858


that `llvm-config.exe` reports that one should link to `zstd.dll.lib` which does not exist on conda-forge.

Is there something we can do to address this at the llvm level instead of requiring all the packages that depend on it to write their own meson files?

### Installed packages

```shell
2025-03-23T19:02:25.9507037Z
2025-03-23T19:02:25.9507761Z environment location: D:\bld\mesalib_1742756351110\_h_env
2025-03-23T19:02:25.9508769Z
2025-03-23T19:02:25.9509143Z
2025-03-23T19:02:25.9510027Z The following NEW packages will be INSTALLED:
2025-03-23T19:02:25.9510513Z
2025-03-23T19:02:25.9511062Z libiconv: 1.18-h135ad9c_1 conda-forge
2025-03-23T19:02:25.9511627Z libllvm-c20: 20.1.1-h3089188_0 conda-forge
2025-03-23T19:02:25.9512626Z libllvm20: 20.1.1-h3089188_0 conda-forge
2025-03-23T19:02:25.9513229Z libxml2: 2.13.6-he286e8c_0 conda-forge
2025-03-23T19:02:25.9513807Z libzlib: 1.3.1-h2466b09_2 conda-forge
2025-03-23T19:02:25.9514373Z llvm: 20.1.1-h249f83d_0 conda-forge
2025-03-23T19:02:25.9514943Z llvm-tools: 20.1.1-h2a44499_0 conda-forge
2025-03-23T19:02:25.9515528Z llvmdev: 20.1.1-h3089188_0 conda-forge
2025-03-23T19:02:25.9516104Z ucrt: 10.0.22621.0-h57928b3_1 conda-forge
2025-03-23T19:02:25.9516669Z vc: 14.3-hbf610ac_24 conda-forge
2025-03-23T19:02:25.9517298Z vc14_runtime: 14.42.34438-hfd919c2_24 conda-forge
2025-03-23T19:02:25.9517878Z zlib: 1.3.1-h2466b09_2 conda-forge
2025-03-23T19:02:25.9518437Z zstd: 1.5.7-hbeecb71_2 conda-forge
2025-03-23T19:02:25.9518827Z
```

### Environment info

```shell
2025-03-23T18:59:04.2294977Z
2025-03-23T18:59:04.2296054Z 'mamba' is running as a subprocess and can't modify the parent shell.
2025-03-23T18:59:04.2297530Z Thus you must initialize your shell before using activate and deactivate.
2025-03-23T18:59:04.2298001Z
2025-03-23T18:59:04.2298267Z
2025-03-23T18:59:04.2299438Z To automatically initialize all future (cmd.exe) shells, run:
2025-03-23T18:59:04.2300634Z $ mamba shell init --shell cmd.exe --root-prefix=~/.local/share/mamba
2025-03-23T18:59:04.2301090Z If your shell was already initialized, reinitialize your shell with:
2025-03-23T18:59:04.2301404Z $ mamba shell reinit --shell cmd.exe
2025-03-23T18:59:04.2301707Z Otherwise, this may be an issue. In the meantime you can run commands. See:
2025-03-23T18:59:04.2301999Z $ mamba run --help
2025-03-23T18:59:04.2302156Z
2025-03-23T18:59:04.2302394Z Supported shells are {bash, zsh, csh, posix, xonsh, cmd.exe, powershell, fish, nu}.
2025-03-23T18:59:05.6098634Z
2025-03-23T18:59:05.6100526Z active environment : base
2025-03-23T18:59:05.6101298Z active env location : D:\Miniforge
2025-03-23T18:59:05.6101988Z shell level : 1
2025-03-23T18:59:05.6102789Z user config file : C:\Users\VssAdministrator\.condarc
2025-03-23T18:59:05.6103489Z populated config files : D:\Miniforge\.condarc
2025-03-23T18:59:05.6104178Z C:\Users\VssAdministrator\.condarc
2025-03-23T18:59:05.6104817Z conda version : 25.1.1
2025-03-23T18:59:05.6105459Z conda-build version : 25.1.2
2025-03-23T18:59:05.6106110Z python version : 3.12.9.final.0
2025-03-23T18:59:05.6106757Z solver : libmamba (default)
2025-03-23T18:59:05.6107417Z virtual packages : __archspec=1=x86_64_v4
2025-03-23T18:59:05.6108061Z __conda=25.1.1=0
2025-03-23T18:59:05.6108675Z __win=10.0.20348=0
2025-03-23T18:59:05.6109323Z base environment : D:\Miniforge (writable)
2025-03-23T18:59:05.6109995Z conda av data dir : D:\Miniforge\etc\conda
2025-03-23T18:59:05.6110642Z conda av metadata url : None
2025-03-23T18:59:05.6111313Z channel URLs : https://conda.anaconda.org/conda-forge/win-64
2025-03-23T18:59:05.6112044Z https://conda.anaconda.org/conda-forge/noarch
2025-03-23T18:59:05.6112708Z package cache : D:\Miniforge\pkgs
2025-03-23T18:59:05.6113359Z C:\Users\VssAdministrator\.conda\pkgs
2025-03-23T18:59:05.6114314Z C:\Users\VssAdministrator\AppData\Local\conda\conda\pkgs
2025-03-23T18:59:05.6115002Z envs directories : D:\Miniforge\envs
2025-03-23T18:59:05.6115632Z C:\Users\VssAdministrator\.conda\envs
2025-03-23T18:59:05.6116317Z C:\Users\VssAdministrator\AppData\Local\conda\conda\envs
2025-03-23T18:59:05.6116971Z platform : win-64
2025-03-23T18:59:05.6117746Z user-agent : conda/25.1.1 requests/2.32.3 CPython/3.12.9 Windows/2022Server Windows/10.0.20348 solver/libmamba conda-libmamba-solver/25.3.0 libmambapy/2.0.8
2025-03-23T18:59:05.6118648Z administrator : True
2025-03-23T18:59:05.6119233Z netrc file : None
2025-03-23T18:59:05.6119845Z offline mode : False
2025-03-23T18:59:05.6120326Z
```

Start by reproducing llvm-config.exe in the reported win-64 environment with the listed llvm and zstd packages. Trace why it reports zstd.dll.lib; done means a documented, reproducible resolution at the LLVM level or a clear determination that dependent packages must handle it.

Written by the indexing model from the issue text.