fix: correct COPY paths in production client Dockerfile (#180)

The production Dockerfile was using incorrect paths for COPY commands.
Build context is ./lablink-client-base but files are in subdirectory
lablink-client-base-image/, so paths must be relative to context.

Fixes:
- COPY install_miniforge.sh → COPY lablink-client-base-image/install_miniforge.sh
- COPY install_nvm.sh → COPY lablink-client-base-image/install_nvm.sh
- COPY start.sh → COPY lablink-client-base-image/start.sh

Error was:
  ERROR: "/start.sh": not found
  ERROR: "/install_miniforge.sh": not found

This only affected main branch builds (production Dockerfile).
Dev Dockerfile already had correct paths.

Verified allocator Dockerfile paths are also correct (context is repo root).

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-authored-by: Claude <[email protected]>

Author: eberrigan

lablink-client-base/lablink-client-base-image/Dockerfile

@@ -123,7 +123,7 @@ USER ${USERNAME}
 WORKDIR /home/${USERNAME}
 
 # Create scripts directory with miniforge, uv, and nvm installation scripts
-COPY install_miniforge.sh  install_nvm.sh /scripts/
+COPY lablink-client-base-image/install_miniforge.sh lablink-client-base-image/install_nvm.sh /scripts/
 
 # Make scripts executable and run them
 RUN sudo chmod +x /scripts/*.sh && \
@@ -141,7 +141,7 @@ RUN uv venv /home/${USERNAME}/.venv && \
     uv pip install --python=/home/${USERNAME}/.venv/bin/python lablink-client-service==${PACKAGE_VERSION}
 
 # Copy the startup script
-COPY start.sh /home/${USERNAME}/start.sh
+COPY lablink-client-base-image/start.sh /home/${USERNAME}/start.sh
 RUN sudo chmod +x /home/${USERNAME}/start.sh
 
 # Run the startup script