feat: run integration tests inside Docker container

- Execute integration tests via docker exec to access cargo-lambda
- Add testdata volume mount for test file access
- Enable COMPOSE_BAKE for potential build performance improvements
- Set CARGO_TERM_COLOR=never for cleaner CI logs
- Replace host-based cargo lambda invoke with container-based execution

Fixes "no such command: lambda" errors in CI by running tests where
cargo-lambda is installed rather than on the bare GitHub Actions runner.

Author: JohnBasrai

.github/workflows/ci.yml

@@ -7,13 +7,16 @@ on:
     branches: [ main ]
 
 env:
-  CARGO_TERM_COLOR: always
+  CARGO_TERM_COLOR: never
 
 jobs:
   test:
     name: Test
     runs-on: ubuntu-latest
 
+    env:
+      COMPOSE_BAKE: true
+
     steps:
     - name: Checkout code
       uses: actions/checkout@v4
@@ -55,4 +58,5 @@ jobs:
         done
 
     - name: Run integration tests
-      run: cargo test --test integration_tests --release
+      run: docker exec aws-lambda-action-filter-lambda-1 \
+          cargo test --test integration_tests --release --quiet

docker-compose.yml

@@ -8,7 +8,8 @@ services:
     ports:
       - "9000:9000"
     volumes:
-      - ./src:/app/src          # hot-reload watch point
+      - ./src:/app/src             # hot-reload watch point for lambda server
+      - ./testdata:/app/testdata   # testdata for lambda invoke
       - ./Cargo.toml:/app/Cargo.toml
       - ./Cargo.lock:/app/Cargo.lock
       - ${CR8S_SCRATCH_DIR:-/var/tmp}/aws/dev-cargo:/usr/local/cargo/registry