Unit test framework types are static

[pboychev-bcom]

Description

The unit test framework types are statically installed as Node.js dependencies downloaded from Maven central.
With the new implementation for configuring the type and version of framework used the types should be dynamically installed to match the configuration.

Steps to Reproduce

1. Add tests in a TypeScript Aria Automation module.
2. Configure the module to use Jest as a test framework.
3. Use Jest specific definitions.
4. Start the transpilation of the code base (via the build process of the module).

Preconditions: [What are the preconditions to reproduce the issue]
Use BTVA version 3.0.0 and later.

Expected behavior: [What you expect to happen]
The build process should pass, including the unit tests.

Actual behavior: [What actually happens]
The transpilation fails due to missing correct type definitions for the used framework + version.

Reproduces how often: [What percentage of the time does it reproduce]
On every build for configured framework other than Jasmine or for newer versions of Jasmine that are not matching the static types coming from the build tools built-in types.

Component/s: [What are the Build Tools for VMware Aria components affected by the issue (e.g. "common/artifact-manager", "maven/plugins/vra-ng", "typescript/vrotest", etc)]

• "typescript/vrotest"
• "typescript/vrotsc"

Affects Build/s: [Which are the Build Tools for VMware Aria releases / builds affected by the issue]
3.0.0 and above.

Environment

Client

• Build Tools for VMware Aria Version:
• Visual Studio Code Version:
• OS Version:

Dependencies

Run: curl -o- https://raw.githubusercontent.com/vmware/build-tools-for-vmware-aria/main/health.sh | bash and paste the output here:

Server

• vRealize Automation Version:
• vRealize Orchestrator Version:
• vRealize Operations Version:
• vRealize Log Insight Version:

Failure Logs

Related issues and PRs

Additional Context