🐛 fix(docker): regenerate package-lock.json in Docker build stages

Fix npm ci sync issues in Docker multi-stage build by ensuring clean
package-lock.json generation in each stage. This prevents Docker build
failures caused by mismatched dependencies between workflow and container.

- Add package-lock.json regeneration in deps, dev, and build stages
- Use --omit=dev flag for production dependencies in deps stage
- Ensure consistent dependency resolution across all Docker stages

Resolves Docker build failure in deployment job where npm ci was failing
due to package-lock.json sync issues.

Author: martinrebo

server/Dockerfile

@@ -16,13 +16,17 @@ RUN adduser -S serveruser -u 1001
 FROM base AS deps
 # Copy package files
 COPY package*.json ./
+# Regenerate package-lock.json to avoid sync issues
+RUN rm -f package-lock.json && npm install --package-lock-only --omit=dev
 # Clean install production dependencies only
 RUN npm ci --omit=dev && npm cache clean --force
 
 # Development stage
 FROM base AS dev
 # Copy package files
 COPY package*.json ./
+# Regenerate package-lock.json to avoid sync issues
+RUN rm -f package-lock.json && npm install --package-lock-only
 # Install all dependencies (including dev dependencies)
 RUN npm ci
 # Copy source code
@@ -39,6 +43,8 @@ CMD ["npm", "run", "dev"]
 FROM base AS build
 # Copy package files
 COPY package*.json ./
+# Regenerate package-lock.json to avoid sync issues
+RUN rm -f package-lock.json && npm install --package-lock-only
 # Install all dependencies
 RUN npm ci
 # Copy source code