Fix the failing upgrades #154

#135

build-test-core is failing — TypeScript 7 is not yet supported by our test toolchain

I looked into the failing build-test-core check. There are two layers to it:

1. Surface error (lockfile out of sync)
package.json was bumped to typescript@^7.0.0 but package-lock.json still pins [email protected], so npm ci fails:

npm error `npm ci` can only install packages when your package.json and package-lock.json are in sync.
npm error Invalid: lock file's [email protected] does not satisfy [email protected]

2. The real blocker (ts-jest does not support TS 7)
Regenerating the lockfile does not fix it. TypeScript 7.0 is the new native ("tsgo") compiler generation, and our test runner ts-jest is incompatible with it:

• [email protected] (latest) declares peer typescript: ">=4.3 <7", so npm ci then hard-fails with ERESOLVE.
• Even bypassing the peer check, npm test crashes because ts-jest cannot consume the TS 7 compiler API:

  TypeError: Cannot read properties of undefined (reading 'readFile')
      at ConfigSet._resolveTsConfig (node_modules/ts-jest/.../config-set.js)
  

• npm view ts-jest peerDependencies confirms no released ts-jest version (latest 29.4.11, next 29.0.0-next.1) allows typescript >=7.

Good news: the source itself is TS 7-ready — tsc (7.0.2) compiles it cleanly (exit 0). The only blocker is the Jest transformer.

Recommendation: hold this bump until ts-jest publishes TypeScript 7 support. Migrating off ts-jest (to swc/babel/vitest) purely to satisfy this Renovate bump would be unjustified test-infra risk (ESM handling, path resolution, @actions/core mocks, diagnostics). Once npm view ts-jest peerDependencies allows typescript >=7 and a local npm ci && npm test && npm run build passes without peer overrides, this can be taken as a normal dependency update.