Fix ci-ets: pin @types/node@18 for the ArkAnalyzer build (#362)

* Fix ci-ets: pin @types/node@18 for the ArkAnalyzer build

ArkAnalyzer's npm install pulls the floating latest @types/node, whose
new d.ts files (e.g. ffi.d.ts) use syntax that ArkAnalyzer's bundled
TypeScript cannot parse, so `npm run build` fails with TS1139/TS1005
errors and the whole ci-ets job dies before any Gradle test runs.
Pin a compatible @types/node major right after npm install.

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

* Fix ci-ets: pin @types/node in the manifest instead of a second npm install

A follow-up `npm install --no-save @types/node@18` re-resolves the npm
tree and prunes ohos-typescript, which ArkAnalyzer's postinstall script
installs with --no-save (it is absent from package.json), so the build
fails with TS2307. Pin @types/node via `npm pkg set` BEFORE the single
`npm install` instead: the pin then survives resolution and postinstall
keeps ohos-typescript in place. Verified locally: `npm run build`
produces out/src/save/serializeArkIR.js.

Author: CaelmBleidd

.github/workflows/ci.yml

@@ -134,6 +134,14 @@ jobs:
           echo "ARKANALYZER_DIR=$(realpath $DEST_DIR)" >> $GITHUB_ENV
           cd $DEST_DIR
 
+          # ArkAnalyzer's bundled TypeScript (ohos-typescript 4.9.5) cannot parse
+          # the d.ts files of the latest floating @types/node (e.g. ffi.d.ts uses
+          # newer syntax and breaks `npm run build` with TS1139 etc.), so pin a
+          # compatible major IN THE MANIFEST before the single `npm install`.
+          # NB: do not run a second `npm install <pkg>` afterwards — it re-resolves
+          # the tree and prunes ohos-typescript, which the postinstall script adds
+          # with --no-save (i.e. it is absent from package.json).
+          npm pkg set 'devDependencies.@types/node=18'
           npm install
           npm run build