Fix dev/image build by adding leeway dependency for npm-tools

Create leeway generic build for dev/npm-tools and use it as a dependency in dev/image:docker build. This resolves the build error where npm-tools files were not accessible during Docker build.

Changes:
- Add dev/npm-tools/BUILD.yaml with generic package containing package.json and package-lock.json
- Add dev/npm-tools:pkg as dependency in dev/image/BUILD.yaml
- Update Dockerfile to use COPY from leeway dependency path (dev-npm-tools--pkg/)

This follows the established pattern used in other builds like install/installer where dependencies are copied from leeway-generated paths.

Co-authored-by: Ona <no-reply@ona.com>

Author: geropl

dev/image/BUILD.yaml

@@ -4,6 +4,7 @@ packages:
     deps:
       - dev/gpctl:app
       - dev/kubecdl:app
+      - dev/npm-tools:pkg
     argdeps:
       - imageRepoBase
     srcs:

dev/image/Dockerfile

@@ -143,7 +143,7 @@ RUN sudo rm -f /usr/bin/npx /usr/local/bin/npx /home/gitpod/.nvm/versions/node/v
     sudo chmod +x /usr/local/bin/npx
 
 # Install npm-tools with locked dependencies
-COPY dev/npm-tools/package.json dev/npm-tools/package-lock.json /opt/npm-tools/
+COPY dev-npm-tools--pkg/package.json dev-npm-tools--pkg/package-lock.json /opt/npm-tools/
 RUN cd /opt/npm-tools && \
     npm ci && \
     for bin in /opt/npm-tools/node_modules/.bin/*; do \

dev/npm-tools/BUILD.yaml

@@ -0,0 +1,9 @@
+packages:
+  - name: pkg
+    type: generic
+    srcs:
+      - "package.json"
+      - "package-lock.json"
+    config:
+      commands:
+        - ["echo", "npm-tools package files"]