Change the target in the cloudbuild.yaml to dev

There were failures because it relied on eslint being installed which is a dev dependency. The main reason we run checks against a production container is to ensure that the exact deployed environment works. Here, we only need build-and-test step as deployment is a manual process so the build isn't producing a production container (I THINK!) and so it should be ok to run tests and linting against a dev env.

Author: jordantomiko

cloudbuild.yaml

@@ -13,7 +13,7 @@ steps:
       - -c
       - |
         docker build \
-          --target production \
+          --target dev \
           -t europe-west1-docker.pkg.dev/${PROJECT_ID}/hubblehq-docker/request \
           .
   - id: 'Run linting'
@@ -24,10 +24,10 @@ steps:
       - |
         docker compose \
         -f docker-compose.yml \
-        --profile production \
+        --profile dev \
         run \
         --rm \
-        production yarn lint
+        dev yarn lint
     waitFor: ['Build image']
 
   - id: 'Run tests'
@@ -38,10 +38,10 @@ steps:
       - |
         docker compose \
         -f docker-compose.yml \
-        --profile production \
+        --profile dev \
         run \
         --rm \
-        production yarn test
+        dev yarn test
     waitFor: ['Build image', 'Run linting']
 
 substitutions: