fix: disable eagle-api route in dev to prevent hostname conflict

- Dev uses single hostname (eagle-dev.apps.silver.devops.gov.bc.ca) for all services
- eagle-public route already claims root path on this hostname
- eagle-api route pointing to rproxy caused 'HostAlreadyClaimed' error
- All /api traffic flows through nginx routing (no separate route needed)

Test/prod are unaffected - they use separate hostnames for API and public.

Author: danieltruong

helm/eagle-api/values-dev.yaml

@@ -6,6 +6,7 @@ image:
   tag: dev
 
 route:
+  enabled: false  # All traffic goes through eagle-public route -> nginx -> /api paths
   host: eagle-dev.apps.silver.devops.gov.bc.ca
 
 resources: