build(docker): add configs to speed up compose up/down/restart

1. In `package.json`, add `--abort-on-container-exit` flag to the npm `start` script. This ensures the `dynamodb-local` container is also killed when the `api` container is stopped, which ensures the db container's port is released and made available for subsequent `up` invocations. Without this, the next `up` will fail bc the port will be unavailable (unless additional action has been taken to free up the port).

2. In `package.json`, change the `start:dist` script to use the `start` script so it doesn't have to repeat the long `--abort-on-container-exit` docker compose flag.

3. In `docker-compose.yaml`, add `stop_grace_period: 2s` to the `api` container's configs. This overrides the default of `10s`, which is unnecessarily long and slows down container killing/restart.

Author: trevor-anderson

docker-compose.yaml

@@ -22,6 +22,7 @@ services:
       AWS_SECRET_ACCESS_KEY: local
       DYNAMODB_ENDPOINT: "http://dynamodb-local:8000"
     tty: true
+    stop_grace_period: 2s # default is 10s
 
   dynamodb-local:
     container_name: dynamodb-local

package.json

@@ -21,8 +21,8 @@
   },
   "type": "module",
   "scripts": {
-    "start": "docker compose up",
-    "start:dist": "API_COMMAND='node dist/index.js' docker compose up",
+    "start": "docker compose up --abort-on-container-exit",
+    "start:dist": "API_COMMAND='node dist/index.js' && npm start",
     "prebuild": "[ -d dist ] && rm -rf dist || true",
     "build": "swc src --out-dir dist --strip-leading-paths",
     "lint": "eslint src",