Allow `triggerPath` triggered packages to be treated as indirect

Right now it's not an option. If you are included via a triggerPath, we consider you directly changed. This was introduced due to .NET, but it doesn't play well with the JS repo, where they really need to know if the package was directly changed in the PR or not. They need to know this because if the file was directly changed, they need to add `--from` to the rush args, `--to` otherwise. Because of the `triggerPaths treated as direct` update, this means that they are running more tests than are actually necessary.

We should make this an additional parameter in `Save-Package-Properties.yml`.