ng-add forces use of NPM to install dependencies even when another package manager is configured in angular.json #513
Description
When you install the package using ng add @testing-library/angular and you have configured another package manager than NPM, the install phase fails.
In the code of the ng-add schematics, the packageManager has a default value set to "npm".
I think if you don't pass the packagerManager option, the NodePackageInstallTask task should use the package manager configured in the angular.json file, right?