#113 address review feedback

Pin node-version to '20.19' in all three CI workflows — ESLint 10 requires
^20.19.0 per its engines field, and 'node-version: 20' on ubuntu-latest
could resolve below that minimum and cause ESLint to refuse to run.

NOTE: The Critical CI failure (run-linting-check) has an upstream root cause
that this commit cannot fix: eslint-plugin-react@7.37.5 (bundled inside
eslint-config-next@16.2.7) uses the ESLint v9 context.getFilename() API
which was removed in ESLint 10. The eslint-plugin-react maintainer has
confirmed this incompatibility (jsx-eslint/eslint-plugin-react#4018) and a
fix PR (#3979) is still open. Until that fix ships and eslint-config-next
bundles a compatible version, ESLint 10 cannot be used with this project.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: b-at-neu

.github/workflows/linting-check.yml

@@ -11,7 +11,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '20'
+          node-version: '20.19'
       - name: Install modules
         run: npm install
       - name: Run linting check

.github/workflows/prettier-check.yml

@@ -11,7 +11,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '20'
+          node-version: '20.19'
       - name: Install modules
         run: npm install
       - name: Run prettier check

.github/workflows/tsc-check.yml

@@ -11,7 +11,7 @@ jobs:
       - name: Set up Node.js
         uses: actions/setup-node@v4
         with:
-          node-version: '20'
+          node-version: '20.19'
       - name: Install dependencies
         run: npm install
       - name: Generate Prisma client