refactor: remove DynamoDB (v2) integration tests

DynamoDB backend is no longer needed - PostgreSQL is the sole backend.

- Remove test/it/dynamo/ (harness, setup, seed data, wiring files)
- Simplify env.js to only build PostgreSQL env vars
- Update CLAUDE.md to reflect PostgreSQL-only IT setup
- Remove it-dynamo input from CI workflow

Author: solaris007

.github/workflows/ci.yaml

@@ -18,6 +18,5 @@ jobs:
       service-name: api-service
       validate-pr-title: true
       docs-lint: true
-      it-dynamo: true
       it-postgres: true
     secrets: inherit

CLAUDE.md

@@ -23,14 +23,11 @@ npx mocha test/path/to/specific.test.js -g "pattern" # Run tests matching patter
 
 ### Integration Tests
 ```bash
-# DynamoDB suite (requires Java 17+)
-npx mocha --require test/it/dynamo/harness.js --timeout 30000 'test/it/dynamo/**/*.test.js'
-
 # PostgreSQL suite (requires Docker + ECR access)
 npx mocha --require test/it/postgres/harness.js --timeout 30000 'test/it/postgres/**/*.test.js'
 
 # Single IT test file
-npx mocha --require test/it/dynamo/harness.js --timeout 30000 test/it/dynamo/sites.test.js
+npx mocha --require test/it/postgres/harness.js --timeout 30000 test/it/postgres/sites.test.js
 ```
 
 ### Documentation
@@ -62,7 +59,7 @@ Request → AWS Lambda → Middleware Stack → Route Matcher → Controller →
 **Middleware Stack** (in order, defined in `src/index.js`):
 1. `authWrapper` - Authentication (JWT, IMS, API Keys, Scoped API Keys)
 2. `logWrapper` - Structured logging
-3. `dataAccess` - DynamoDB access layer (`@adobe/spacecat-shared-data-access`)
+3. `dataAccess` - Data access layer (`@adobe/spacecat-shared-data-access`)
 4. `bodyData` - Request body parsing
 5. `multipartFormData` - File upload handling
 6. `enrichPathInfo` - Path parameter extraction
@@ -309,7 +306,7 @@ Tests mirror source structure in `test/`:
 - `test/routes/` - Route matching tests
 - `test/support/` - Utility tests
 - `test/e2e/` - End-to-end tests
-- `test/it/` - Integration tests (DynamoDB v2 + PostgreSQL v3)
+- `test/it/` - Integration tests (PostgreSQL)
 
 ### Standard Test Pattern
 
@@ -369,27 +366,24 @@ describe('Sites Controller', () => {
 
 **Location**: `test/it/` — see [test/it/README.md](test/it/README.md) for full documentation.
 
-Integration tests validate the full API request lifecycle against real database backends — no mocks. Every test runs identically against DynamoDB (v2) and PostgreSQL (v3) to ensure migration parity.
+Integration tests validate the full API request lifecycle against a real PostgreSQL database - no mocks.
 
-**Architecture**: Shared test factories in `test/it/shared/tests/` are wired to backend-specific harnesses:
+**Architecture**: Shared test factories in `test/it/shared/tests/` are wired to the PostgreSQL harness:
 
 ```
-shared/tests/sites.js → dynamo/sites.test.js   (uses DynamoDB Local + v2 data access)
-                       → postgres/sites.test.js (uses Docker PostgreSQL + PostgREST)
+shared/tests/sites.js → postgres/sites.test.js (uses Docker PostgreSQL + PostgREST)
 ```
 
 **Key concepts**:
 - **Seed IDs**: All test data uses canonical UUIDs from `shared/seed-ids.js`
 - **Three auth personas**: `admin` (full access), `user` (ORG_1 only), `trialUser` (trial endpoints)
 - **Data reset**: Each `describe` block calls `before(() => resetData())` to ensure isolation
-- **Backend-specific options**: Use `options` parameter for v3-only features (e.g., `{ skipAsyncJobTests: true }` for DynamoDB)
-- **Seed data format**: DynamoDB uses camelCase, PostgreSQL uses snake_case
-- **v3-only entities**: `AsyncJob` only exists in PostgreSQL — DynamoDB tests skip these
+- **Seed data format**: snake_case in `postgres/seed-data/`
 
 ### Test Requirements
 
 - **Behavior changes must include unit tests** - mark as Critical if missing
-- **New or modified endpoints must include integration tests** in `test/it/` — add shared test logic in `shared/tests/`, seed data in both `dynamo/seed-data/` and `postgres/seed-data/`, and wiring files in both backend directories
+- **New or modified endpoints must include integration tests** in `test/it/` — add shared test logic in `shared/tests/`, seed data in `postgres/seed-data/`, and a wiring file in `postgres/`
 - Mock external dependencies (databases, HTTP calls, queues) in unit tests
 - Test access control paths (authorized, forbidden, admin-only)
 - Test DTO transformations
@@ -500,10 +494,10 @@ return internalServerError('Internal error occurred');
 9. Write unit tests in `test/controllers/`
 10. Write integration tests in `test/it/`:
     - Add seed IDs to `test/it/shared/seed-ids.js`
-    - Add seed data to both `dynamo/seed-data/` (camelCase) and `postgres/seed-data/` (snake_case)
-    - Register seeds in both `dynamo/seed.js` and `postgres/seed.js`
+    - Add seed data to `postgres/seed-data/` (snake_case)
+    - Register seeds in `postgres/seed.js`
     - Write shared test factory in `test/it/shared/tests/`
-    - Create wiring files in both `dynamo/` and `postgres/`
+    - Create wiring file in `postgres/`
 11. Run `npm run docs:build` to generate documentation
 12. Run `npm test` to verify unit tests pass
 13. Run IT suites to verify integration tests pass (see Integration Tests commands above)