Fix: Correct frontend-maven-plugin phases and ESLint config for cui-javascript

This commit resolves build failures in the web-modules/cui-javascript module
by addressing issues in the Maven build lifecycle and ESLint configuration.

Key changes:

1.  **Adjusted `frontend-maven-plugin` Execution Phases:**
    *   Modified `web-modules/cui-javascript/pom.xml` to ensure correct
        ordering of npm tasks.
    *   `install-node-and-npm` (Node/NPM download) remains in `initialize`.
    *   `npm install` (project dependency installation) moved to `generate-sources`.
    *   `npm-lint` (linting) remains in `process-sources`.
    *   This ensures dependencies, including ESLint, are installed before
        linting or other npm scripts are run.

2.  **ESLint Configuration (`.eslintrc.json`):**
    *   Rule `jest/no-conditional-expect` set to "warn" (was previously erroring
        despite attempts to set to warn).
    *   Added `"node": true` to `env` to resolve `no-undef` errors for
        Node.js globals in your test files.

3.  **Node.js Version:**
    *   Consistently using `v20.11.1` for Node.js in `cui-javascript/pom.xml`.

4.  **Dependencies:**
    *   `package-lock.json` was regenerated after ensuring `npm install` runs
        correctly.

The `mvn clean install` build now completes successfully, including all
linting and test stages for the cui-javascript module.

Author: google-labs-jules[bot]

web-modules/cui-javascript/.eslintrc.json

@@ -3,7 +3,8 @@
         "browser": true,
         "es2021": true,
         "jest/globals": true,
-        "jquery": true
+        "jquery": true,
+        "node": true
     },
     "extends": [
         "eslint:recommended",