[pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

Author: pre-commit-ci[bot]

news/2025-05-29-cuda-118.md

@@ -17,12 +17,12 @@ building CUDA 11.8 on a per-feedstock basis where this is necessary or beneficia
 
 The above-mentioned contraints are mainly:
 
-* it complicates our pinning due to needing to switch images and compilers with 11.8.
-* it keeps us from [migrating](https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/7005)
+- it complicates our pinning due to needing to switch images and compilers with 11.8.
+- it keeps us from [migrating](https://github.com/conda-forge/conda-forge-pinning-feedstock/pull/7005)
   to newer CUDA 12.x versions necessary to support new architectures.
-* it's not compatible with VS2022, which is due to become the default toolchain on windows
+- it's not compatible with VS2022, which is due to become the default toolchain on windows
   in conda-forge soon (the previous VS2019 has reached end-of-life more than a year ago).
-* it complicates our infrastructure in several places, due to the big differences between the
+- it complicates our infrastructure in several places, due to the big differences between the
   before/after of the new CUDA architecture.
 
 After we have removed CUDA 11.8 from the pinning, any feedstock still building that version