C1: alloy v1.16.0 — bump kustomization tags

Both container images published manually (CI on indri couldn't complete
due to host RAM pressure — 7.2 GB in macOS memory compressor causing
~10–100x slowdown on memory-touching work, see separate ticket thread):

  - registry.ops.eblu.me/blumeops/alloy:v1.16.0-26a3ab5
    (dagger build, run locally on gilbert via container.py)
  - registry.ops.eblu.me/blumeops/alloy:v1.16.0-26a3ab5-nix
    (nix build, run on ringtail's nix-container-builder)

Both images built from the alloy-v1.16.0 branch tip 26a3ab5b. After
PR squash-merge, follow up with a C0 to rebuild from the main SHA and
bump tags to a [main]-marked variant per the squash-merge convention.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

argocd/manifests/alloy-k8s/kustomization.yaml

@@ -10,7 +10,7 @@ resources:
 
 images:
   - name: registry.ops.eblu.me/blumeops/alloy
-    newTag: v1.14.0-fd0bebb
+    newTag: v1.16.0-26a3ab5
 
 configMapGenerator:
   - name: alloy-config

argocd/manifests/alloy-ringtail/kustomization.yaml

@@ -10,7 +10,7 @@ resources:
 
 images:
   - name: registry.ops.eblu.me/blumeops/alloy
-    newTag: v1.14.0-fd0bebb-nix
+    newTag: v1.16.0-26a3ab5-nix
 
 configMapGenerator:
   - name: alloy-config

argocd/manifests/alloy-tracing-ringtail/kustomization.yaml

@@ -9,7 +9,7 @@ resources:
 
 images:
   - name: registry.ops.eblu.me/blumeops/alloy
-    newTag: v1.14.0-fd0bebb-nix
+    newTag: v1.16.0-26a3ab5-nix
 
 configMapGenerator:
   - name: alloy-tracing-config