LLVM v19.1.0

[h-vetinari]

Blockers for merging this PR and thus enabling the compilers in conda-forge (indentation denotes dependency):

• libcxx v19.1.0 libcxx-feedstock#195
• llvmdev v19.1.0 llvmdev-feedstock#288
  • clangdev v19.1.0 clangdev-feedstock#318 (also needs libcxx)
    • Build for LLVM 19 cctools-and-ld64-feedstock#78 (only major version)
    • compiler-rt v19.1.0 compiler-rt-feedstock#122
      • openmp v19.1.0 openmp-feedstock#144
  • lld v19.1.0 lld-feedstock#105

Related feedstocks for LLVM 19.1.0 support more generally:

• add clang 19.1; remove patch-level pinning clang-win-activation-feedstock#44 (needs this PR; only major version)
• add clang 19.1 ctng-compiler-activation-feedstock#131 (needs this PR; only major version)
• flang v19.1.0 flang-feedstock#72 (needs compiler-rt, mlir)
• flang-activation v19.1.0 flang-activation-feedstock#1 (needs flang, lld)
• add clang 19 libcxx-testing-feedstock#15 (needs this PR; only major version)
• lldb v19.1.0 lldb-feedstock#71 (needs this PR)
• mlir v19.1.0 mlir-feedstock#81 (needs llvmdev)
• mlir-python-bindings v19.1.0 mlir-python-bindings-feedstock#37 (needs this PR)
• build for clang 19.1; don't pin to patch-level r_clang_activation-feedstock#8 (needs clang-win-activation)

[conda-forge-webservices]

Hi! This is the friendly automated conda-forge-linting service.

I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

[github-actions]

Hi! This is the friendly conda-forge automerge bot!

I considered the following status checks when analyzing this PR:

• linter: passed
• azure: passed

Thus the PR was passing and merged! Have a great day!