"ERROR Resource path must not end with '/' but is '.../'" must be improved

[kwin]

Currently if one referenced resource ends with a slash the following exception is logged

[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  49.602 s
[INFO] Finished at: 2020-03-12T09:33:12+01:00
[INFO] ------------------------------------------------------------------------
[DEBUG] No threads registered for execution at the end of the build
[ERROR] Failed to execute goal org.apache.jackrabbit:filevault-package-maven-plugin:1.1.0:validate-package (default-validate-package) on project nc-website-components-package: Execution default-validate-package of goal org.apache.jackrabbit:filevault-package-maven-plugin:1.1.0:validate-package failed: Resource path must not end with '/' but is '..../' -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.apache.jackrabbit:filevault-package-maven-plugin:1.1.0:validate-package (default-validate-package) on project nc-website-components-package: Execution default-validate-package of goal org.apache.jackrabbit:filevault-package-maven-plugin:1.1.0:validate-package failed: Resource path must not end with '/' but is '/libs/core/wcm/components/teaser/v1/teaser/

This error message must be improved to at least emit the file path where the error occurred!
Also the debug log level does not help much as the previous output is
[DEBUG] ValidationViolation: "Validating jcr file '<some jcr file>'..." which is not the failing file but the previous one!

The issue can be easily reproduced by setting the value sling:resourceSuperType on a component definition to a value like core/wcm/components/teaser/v1/teaser/

The situation will improve with the upcoming FileVault 3.4.4 (https://issues.apache.org/jira/browse/JCRVLT-406)