LIME-1864 prefer esbuild over vite for lambda builds

- add example metrics
- add example logging
- remove vite config
- remove makefile
- enable experimental decorators in tsconfig
- update deploy template to use `esbuild` build method
- align GHA with FE

Author: nlsteers

.github/actions/node-setup/action.yml

@@ -0,0 +1,16 @@
+name: Node project setup
+description: Checkout and install dependencies
+
+runs:
+  using: composite
+  steps:
+    - name: Node setup
+      uses: actions/setup-node@v6
+      with:
+        node-version-file: '.nvmrc'
+        cache: 'npm'
+        package-manager-cache: true
+
+    - name: Install dependencies
+      run: npm ci
+      shell: bash

.github/workflows/check-pr.yml

@@ -0,0 +1,76 @@
+name: PR check
+
+on:
+  pull_request:
+    types:
+      - opened
+      - reopened
+      - ready_for_review
+      - synchronize
+
+jobs:
+  pre-commit:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Pre-commit checks
+        uses: govuk-one-login/github-actions/code-quality/run-pre-commit@3b0015c58dd0e19e1572fda59dda4184df387d1e
+        with:
+          all-files: true
+
+  static-checks:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+
+      - name: Setup Node
+        uses: ./.github/actions/node-setup
+
+      - name: Lint
+        run: npm run lint
+
+      - name: Format
+        run: npm run format
+
+      - name: Type check
+        run: npm run type-check
+
+  unit-tests:
+    runs-on: ubuntu-latest
+    permissions:
+      contents: read
+    needs: static-checks
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v6
+        with:
+          fetch-depth: 0 # required for sonar
+
+      - name: Setup Node
+        uses: ./.github/actions/node-setup
+
+      - name: Unit tests
+        run: npm run test:coverage
+
+      - name: Sonar scan # runs after unit tests in order to consume coverage report
+        uses: SonarSource/sonarqube-scan-action@v7.0.0
+        env:
+          SONAR_TOKEN: ${{ secrets.SONAR_TOKEN }}
+
+  merge-status:
+    runs-on: ubuntu-latest
+    needs: [pre-commit, static-checks, unit-tests]
+    if: always()
+    steps:
+      - run: |
+          failed=()
+          [[ "${{ needs.pre-commit.result }}" != "success" ]] && failed+=("pre-commit")
+          [[ "${{ needs.static-checks.result }}" != "success" ]] && failed+=("static-checks")
+          [[ "${{ needs.unit-tests.result }}" != "success" ]] && failed+=("unit-tests")
+
+          if [[ ${#failed[@]} -gt 0 ]]; then
+            echo "The following jobs failed: ${failed[*]}"
+            exit 1
+          fi

.github/workflows/pr-check.yml

@@ -1 +1,2 @@
 ignore-scripts=true
+save-exact=true

.github/workflows/run-sonar-scan.yml

@@ -30,9 +30,6 @@ See the Lime onboarding guide for detailed setup instructions.
 ##### Install dependencies
 `npm ci`
 
-### Build
-`npm run build`
-
 ### Testing
 
 ### Run all tests
@@ -63,14 +60,15 @@ To run manually on all files
 `npm run lint:fix`
 
 ### Formatting
+
 `npm run format`
 `npm run format:fix`
 
 ## Local Development
 
-The project uses Vite for building and Vitest for testing. All source code is in TypeScript and follows ESLint configuration with Prettier formatting.
+The project uses `esbuild` for building and `vitest` for unit testing. All source code is in TypeScript and follows ESLint configuration with Prettier formatting.
 
-The custom Vite build uses a Makefile pattern referenced in `template.yaml` under each Lambda's `Metadata` section and handles TypeScript compilation and dependency bundling. When adding a new lambda the Makefile must be updated too.
+`esbuild` config is per handler, is managed in `template.yaml` under each Lambda's `Metadata` section and handles TypeScript compilation and dependency bundling.
 
 ### Deployment into Development environment
 
@@ -90,7 +88,6 @@ To skip canaries such as when releasing urgent changes to production, set the la
 Note: To update LambdaDeploymentPreference, update the LambdaCanaryDeployment pipeline parameter in the [identity-common-infra repository](https://github.com/govuk-one-login/identity-common-infra/tree/main/terraform/lime/open-banking). To update the LambdaDeploymentPreference for a stack in dev using sam deploy, parameter override needs to be set in the [deploy script](./deploy.sh).
 `--parameter-overrides LambdaDeploymentPreference=<define-strategy> \`
 
-
 ## Parameter prefix
 
 This allows a deploying stack to use parameters of another stack.
@@ -104,7 +101,6 @@ Can also be used with the following limitations in development.
 - Existing stack parameters values if changed will trigger behaviour changes in the stack with the prefix enabled.
 - Existing stack if deleted will cause errors in the deployed stack.
 
-
 ## Quality Gate Tags
 
 All API tests should be tagged with `@QualityGateIntegrationTest`. If a test runs in our pipelines (ie in Build), and tests live features, we should tag them with `@QualityGateRegressionTest`.