Have NodePackageInstallTask use project directory if no directory specified

# 🚀 Feature request

### Command (mark with an `x`)

- [x] new
- [ ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [x] add
- [ ] update
- [ ] lint
- [ ] extract-i18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

### Description

A clear and concise description of the problem or missing capability...

`NodePackageInstallTask` is frequently used by add tasks such as `ng-add` in `@angular/material`. If a schematic like this is called from a custom `ng-new` schematic using `externalSchematic` the install fails because it is run from some non-project directory rather than from inside the newly created project directory.

### Describe the solution you'd like

If you have a solution in mind, please describe it.

Since schematics knows the location of `package.json` it should by default run `NodePackageInstallTask` from that same directory rather than using the working directory.

This would unfortunately qualify as a "breaking" change so a configuration option might be necessary to allow for the "old" (current) behavior once this change is made.

### Describe alternatives you've considered

Have you considered any alternative solutions or workarounds?
The only work-around I've been able to do is essentially replicating the behaviors of third-party schematic "add" tasks within my custom schematic and then running install after the fact which is less than ideal.

Suchen Sie NodePackageInstallTask und die Handhabung des package.json-Pfads im Angular CLI-Schematics-Code. Reproduzieren Sie das externalSchematic ng-new-Szenario und überprüfen Sie anschließend, dass new- und add-Tasks standardmäßig aus dem neu erstellten Projektverzeichnis installieren und dass die angeforderte Kompatibilitätsoption das bestehende Verhalten beibehält.

Vom Indexierungsmodell aus dem Issue-Text verfasst.