chore: upgrade TypeScript to 5.8.3 in v5

[soberm]

Description of changes

Routine compiler modernization for v5-stable: upgrade TypeScript from 3.8.3 to 5.8.3 across the monorepo, bringing this branch in line with the compiler already used on main (v6).

ts-jest@24 cannot compile TypeScript 5 — it depends on ts.getMutableClone, which was removed in TS 5.0 — so the Jest toolchain is moved to the 29.x line to match the stack main already uses. All accompanying changes are the minimal, behavior-preserving adjustments the newer compiler and test runner require (no feature or logic changes; AWS SDK / Predictions dependencies untouched).

Dependency / tooling bumps

• Root package.json: typescript 3.8.3 → 5.8.3; jest, ts-jest, @types/jest, babel-jest, jest-config → 29.x; add jest-environment-jsdom@29; add @babel/core to resolutions.
• Local typescript pin 5.0.2 → 5.8.3: api, api-graphql, api-rest, core, storage.
• tslib ^1 → ^2 (required by TS 5 helper emit): analytics, geo, predictions.
• Per-package Jest config migrated to the ts-jest 29 transform tuple format (globals['ts-jest'] → transform, tsConfig → tsconfig, drop removed testURL): analytics, api, api-graphql, api-rest, auth, aws-amplify, cache, core, datastore, datastore-storage-adapter, geo, interactions, predictions, pubsub, pushnotification, storage, and amazon-cognito-identity-js/jest.config.js, notifications/jest.config.js.
• @types/jest / babel-jest line bumps in pushnotification and aws-amplify-react-native.

Source changes (behavior-preserving, required by TS 5)

• packages/auth/src/Auth.ts — explicit new Promise<void> / resolve(undefined).
• packages/datastore/src/predicates/sort.ts — String(field) for symbol index.
• packages/datastore/src/predicates/next.ts — PersistentModel generic constraint.
• packages/datastore/src/sync/processors/subscription.ts — explicit new Promise<void>.
• packages/datastore/src/sync/processors/sync.ts — Record<string, any> on computed-key destructure.
• packages/datastore/src/storage/adapter/StorageAdapterBase.ts — Partial<any> cast.
• packages/datastore/src/storage/relationship.ts — PersistentModel generic constraint.
• packages/datastore/src/types.ts — Extract<…, { field: any }> for stricter indexed access.
• packages/datastore/src/util.ts — applyPatches argument cast (immer Draft<T>).
• packages/datastore-storage-adapter/src/common/SQLiteUtils.ts — String(field) cast.
• packages/geo/src/util.ts — build regex via new RegExp(..., 'iu') (TS 5.5 validates flags vs es5 target).
• packages/interactions/src/Providers/AWSLexProviderHelper/utils.native.ts — build regex via new RegExp(..., 's').
• packages/pubsub/src/Providers/AWSAppSyncRealTimeProvider/index.ts — String(authenticationType).
• packages/pubsub/src/vendor/paho-mqtt.js — JSDoc @type {any} for declaration emit.
• packages/storage/src/providers/AWSS3Provider.ts — drop always-nullish null ?? operand.

Test changes (required by Jest 29 / TS 5)

• __tests__ updated for Jest 29: removed jasmine.* globals (jasmine.any → expect.any), spyOn → jest.spyOn, CommonJS __esModule interop on mock factories, and setImmediate → setTimeout. Affected packages: amazon-cognito-identity-js, api-graphql, api-rest, auth, aws-amplify, cache, core, datastore, interactions, predictions, pubsub, storage.
• packages/datastore/jest.setup.js (new) — restores Node's setImmediate/clearImmediate for fake-indexeddb under jest-environment-jsdom@29.
• Snapshot refreshes in datastore reflecting TS 5 compiled output.
• lockfile updated for the new resolutions.

Issue #, if available

N/A

Description of how you validated changes

Using Node 24 (the version this repo's CI uses):

• lerna run build — all 20 packages build, declarations emitted, 0 compiler errors.
• lerna run test — every package's existing test script runs and passes (including the tslint + coverage gates), plus yarn test:license and yarn test:github-actions.

Checklist

• PR description included
• yarn test passes
• Tests are changed or added
• Relevant documentation is changed or added (and PR referenced)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 4c5f4d5

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR