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

Dockerfile

@@ -9,7 +9,7 @@ ENV LANGUAGE='en_US:en'
 
 # Configuration Quarkus
 ENV QUARKUS_PROFILE=prod
-ENV QUARKUS_HTTP_PORT=8086
+ENV QUARKUS_HTTP_PORT=8080
 ENV QUARKUS_HTTP_HOST=0.0.0.0
 
 # Configuration Backend UnionFlow
@@ -35,8 +35,8 @@ COPY --chown=appuser:appuser target/*-runner.jar /app/app.jar
 
 USER appuser
 
-# Exposer le port 8086
+# Exposer le port 8080
-EXPOSE 8086
+EXPOSE 8080
 
 # Variables JVM optimisées
 ENV JAVA_OPTS="-Xmx1g -Xms512m \
@@ -56,4 +56,4 @@ ENTRYPOINT ["sh", "-c", "exec java $JAVA_OPTS -jar /app/app.jar"]
 
 # Health check sur le bon port
 HEALTHCHECK --interval=30s --timeout=10s --start-period=120s --retries=3 \
-  CMD curl -f http://localhost:8086/q/health/ready || exit 1
+  CMD curl -f http://localhost:8080/q/health/ready || exit 1

src/main/resources/application-prod.properties

@@ -2,7 +2,7 @@
 # Ce fichier est utilisé avec le profil Quarkus "prod"
 
 # Configuration HTTP
-quarkus.http.port=8086
+quarkus.http.port=8080
 quarkus.http.host=0.0.0.0
 quarkus.http.root-path=/
 quarkus.http.so-reuse-port=true