Upgrade TypeScript to latest 5.x and Jest to latest 29.x

[vojtechszocs]

• bump TypeScript to 5.9.3
• bump Jest to 29.7.0
  • 📝 can't use Jest 30 due to ts-jest issue Did Jest v30 have been tested? kulshekhar/ts-jest#4625
• bump Jest related packages
  • ts-jest to 29.4.10
  • jest-axe to 10.0.0
• bump @types/jest to latest 29.x
  • 📝 we still need @types/jest for global test types like describe, it, expect, jest.fn etc.
• add jest-environment-jsdom
  • 📝 starting with Jest 28 this needs to be an explicit dependency
• update jest.mocked calls in tests
  • 📝 using jest.mocked(fn) since in Jest 29 shallow mocking is the default setting
• bump API Extractor & API Documenter to latest 7.x
  • 📝 fix top-level api-extractor script to refer to root node_modules/typescript/lib
• bump ts-node to latest 10.x

[vojtechszocs]

Note - when running e.g. (cd packages/lib-core ; yarn api-extractor) this has resulted in

--typescript-compiler-folder packages/lib-core/node_modules/typescript/lib

which does not exist, so we're using $PROJECT_CWD which always points to workspace root directory.

[logonoff]

/lgtm

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: logonoff, vojtechszocs

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [logonoff,vojtechszocs]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-merge-bot]

/retest-required

Remaining retests: 0 against base HEAD 2cf9de4 and 2 for PR HEAD 63aa790 in total

[openshift-ci]

@vojtechszocs: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/all-packages	63aa790	link	true	/test all-packages

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.