Fix conda network failures on GHA workflows
Miniconda is used on GHA workflows to build and test conda packages. Several workflows needed to be re-run after facing network failures like the one below- https://github.com/numba/llvmlite/actions/runs/18354973306/job/52284561372
A solution could be to update conda config params to workflows similar to - https://github.com/numba/numba/blob/main/buildscripts/incremental/setup_conda_environment.sh
increased network related failures - https://github.com/numba/llvmlite/actions/runs/18659074351/attempts/1 https://github.com/numba/llvmlite/actions/runs/18149557773/job/53202079287?pr=1311
In RAPIDS we have https://github.com/rapidsai/gha-tools/blob/main/tools/rapids-conda-retry to make network failures much less likely to turn into a fatal error - perhaps this is worth incorporating into Numba / llvmlite scripts?