Restore the five artifacts that were committed as LFS pointers

ea12071 rebuilt the torch212/213 CUDA variants. The five it did not rebuild --
both Metal variants and the three torch211 CUDA ones -- were unsmudged pointer
text in that working tree, so `git lfs clean` stored the pointer itself as the
object: a 132/133-byte .so that fails to dlopen with 'slice is not valid mach-o
file'. Restored from the last commit where each pointer described a real binary.

build/torch211-cxx11-cu126-x86_64-linux/_gguf_kernels_cuda_e4e2164.abi3.so

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b13c3193a71b1801478effbc94a8007b706c1ec6f140f9567349d97bcef68ace
-size 133
+oid sha256:4bc09a45aabd708b54f9ce83b5ec9627ed185826b64aeb2b5673f46cad4c508e
+size 24799632

build/torch211-cxx11-cu128-x86_64-linux/_gguf_kernels_cuda_e4e2164.abi3.so

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:039423d3e913e348225f13e3764e50c4cd8feb79617f045003a447e63bafe609
-size 133
+oid sha256:b71394062f24b9601e17ee704b313494487bbe77b8d20f54adbfd52665d9f300
+size 37124624

build/torch211-cxx11-cu130-x86_64-linux/_gguf_kernels_cuda_e4e2164.abi3.so

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:e8af7132e7c0e5ee536b2537b538b880325d8b00ac1fa8e53aa3914f537d0149
-size 133
+oid sha256:5b19aec224f81561100e3133d414393779bacfabf2c703040e64b95fe0b69cef
+size 37378504

build/torch212-metal-aarch64-darwin/_gguf_kernels_metal_0becb0a.abi3.so

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:b15d061c06a3be61c1b7039d153b6a791d8bb2f7bc972a44fa33e575642ecbd0
-size 132
+oid sha256:b369cc5b468e2fd3b9ac84f5c63897a52bc25e0381c37104d11d0956f5ad4dd9
+size 7403104

build/torch213-metal-aarch64-darwin/_gguf_kernels_metal_0becb0a.abi3.so

@@ -1,3 +1,3 @@
 version https://git-lfs.github.com/spec/v1
-oid sha256:6346a66092b922568c84e4ed636157542f3b9b529d6b5680a03a79bc81e34712
-size 132
+oid sha256:59d0c2717f44308bc965b82e520cce45b0a6f7e496bc9e95dfc2367dbc75f441
+size 7403104