AEM as Cloud Service - Non-production pipeline failing when using Angular

### Expected Behaviour
Being able to execute a non-production pipeline without errors.

### Actual Behaviour
A non-production pipeline is failing when trying to run ui.frontend `npm test`. I attached a full log from the pipeline.

### Reproduce Scenario (including but not limited to)
Executing a non-production pipeline for a project using Angular and archetype 29.
I was able to reproduce using WSL 2.0 as well, running `mvn clean install -PautoInstallSinglePackage`.

#### Steps to Reproduce
Create a new project using angular as a frontend module:

`mvn -B archetype:generate "-D archetypeGroupId=com.adobe.aem" "-D archetypeArtifactId=aem-project-archetype" "-D archetypeVersion=29" "-D appTitle=aem_angular" "-D appId=aem-angular" "-D groupId=com.aem.angular" "-D aemVersion=cloud" "-D frontendModule=angular" "-D includeExamples=y" "-D amp=n" "-D enableSSR=n" "-D language=pt" "-D singleCountry=n" "-D includeDispatcherConfig=y" "-D country=br"`

#### Platform and Version
AEM as Cloud Service - latest version.
Archetype 29

#### Logs taken while reproducing problem
[build_maven_build.log](https://github.com/adobe/aem-project-archetype/files/7220273/build_maven_build.log)

Any help is appreciated.

Start with the attached build_maven_build.log and reproduce the generated Angular project using the archetype command, then run ui.frontend npm test and mvn clean install -PautoInstallSinglePackage. Compare the failure in the non-production pipeline with the local output; done means the generated Angular project completes both commands without errors.

Written by the indexing model from the issue text.