FSPackageRegistry should allow forced application scoping of PackageInstallations

In contrast to JCR Package Registry the installation of Packages via FS PackageRegistry is designed for application deployment procedures. As these installations are mostly hidden behind the implementation details of ExecutionPlan I propose the introduction of a flag that implicitly decorates the filter with the already existing ScopedFilter.

Although it is tempting to perform the same for application scoping on the JCR Registry the various ways to tricker package installations make it harder to introduce a similar configuration that catches all scenarios - as ExecutionPlan is not a scenario for installation via PackageManager (the still dominant scenario of installing packages at runtime) - the consuming code may decorate and set the decorated workspaceFilter, making it an explicit choice of the consuming code.