Bring nearle stack and routing manifests under Flux management

- manifests/core/kustomization.yaml: add ingress-unified.yaml and
  traefik-middlewares.yaml, which were never in any kustomization and so
  were never actually GitOps-managed - the queue.workolik.com routing fix
  from c38a367 turned out to be live already (likely applied manually
  before this session), but was completely undetected by Flux until now.
  Dropped the redundant top-level `namespace: core` override since every
  existing resource already sets its own namespace explicitly, and the
  two new files span alaska/nearle.
- manifests/nearle/kustomization.yaml + clusters/production/apps-nearle.yaml:
  same GitOps treatment already applied to alaska/core, so a fiesta/jupiter/
  atlantis/titan/ariane version bump in git now auto-deploys instead of
  requiring manual kubectl apply.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

manifests/core/kustomization.yaml

@@ -1,7 +1,10 @@
 apiVersion: kustomize.config.k8s.io/v1beta1
 kind: Kustomization
 
-namespace: core
+# No top-level `namespace:` override - every resource below (including
+# ingress-unified.yaml, which spans alaska and nearle) already sets its own
+# metadata.namespace explicitly. A blanket override here would silently
+# force cross-namespace resources into "core" and break their backend refs.
 
 resources:
   - core-namespace.yaml
@@ -10,3 +13,5 @@ resources:
   - worker-script.yaml
   - workers.yaml
   - worker-pdb.yaml
+  - ingress-unified.yaml
+  - traefik-middlewares.yaml