Maven Build Warnings with latest filevault-package-maven-plugin

### Expected Behaviour
No maven build warnings.

### Actual Behaviour
With the recent update to update `filevault-package-maven-plugin` to version `1.3.6` in https://github.com/adobe/aem-project-archetype/pull/1177/files there are some warnings in the default maven build of an AEM project created from the archetype:

```
// ui.apps.structure package
[WARNING] ValidationViolation: Filter root's ancestor '/content/dam' is not covered by any of the specified dependencies nor a valid root. @ META-INF\vault\filter.xml, validator: jackrabbit-filter
[WARNING] ValidationViolation: Package of type 'MIXED' is legacy. Use one of the other types instead! @ META-INF\vault\properties.xml, validator: jackrabbit-packagetype
[WARNING] ValidationViolation: Found orphaned filter entries: entry with root '/apps', entry with root '/apps/mysite', entry with root '/apps/sling', entry with root '/apps/cq', entry with root '/apps/dam', entry with root '/apps/wcm', entry with root '/apps/msm', entry with root '/apps/settings', entry with root '/content/dam/mysite', validator: jackrabbit-filter

// ui.content package
[WARNING] ValidationViolation: Filter root's ancestor '/content/dam/mysite' is not covered by any of the specified dependencies nor a valid root. @ META-INF\vault\filter.xml, validator: jackrabbit-filter
[WARNING] ValidationViolation: Ancestor node '/content/dam/mysite' is not covered by any of the filter rules. Preferably depend on a package that provides this node or include it in the filter rules! @ jcr_root\content\dam\mysite\.content.xml, validator: jackrabbit-filter

// "all" package
[WARNING] Found duplicate file 'META-INF\vault\definition\.content.xml' from sources 'src\main\content\META-INF\vault\definition\.content.xml' and 'target\vault-work\META-INF\vault\definition\.content.xml'.
[WARNING] ValidationViolation: Found orphaned filter entries: entry with root '/apps/mysite-vendor-packages', validator: jackrabbit-filter
```

Reproduce the default archetype Maven build with filevault-package-maven-plugin 1.3.6 and inspect the generated ui.apps.structure, ui.content, and all packages. Start with META-INF/vault/filter.xml, properties.xml, jcr_root/content/dam/mysite/.content.xml, and the duplicate definition/.content.xml paths shown in the warnings. Done means the default build completes without these validation or duplicate-file warnings.

Written by the indexing model from the issue text.