Fix: Change application port from 8086 to 8080 for lionsctl compatibility

lionsctl pipeline generates manifests with port 8080 by default and doesn't
respect custom port configuration in .lionsctl.yaml. Changing the application
to use port 8080 fixes the health check failures.

Changes:
- application-prod.properties: quarkus.http.port=8080
- Dockerfile: EXPOSE 8080, HEALTHCHECK on port 8080
- .lionsctl.yaml: port 8080 in all configurations

This fixes the pod restart loop caused by liveness/readiness probes
checking port 8080 while the app was listening on port 8086.

.lionsctl.yaml

@@ -2,7 +2,7 @@
 deployment:
   replicas: 1
   domain: unionflow.lions.dev
-  port: 8086
+  port: 8080
   environment: production
 
 resources:
@@ -17,8 +17,8 @@ health:
   liveness:
     initialDelaySeconds: 120
     periodSeconds: 10
-    port: 8086
+    port: 8080
   readiness:
     initialDelaySeconds: 60
     periodSeconds: 5
-    port: 8086
+    port: 8080