Allow whitespaces in the configuration of the plugin

[royteeuwen]

The list of whitelisted resource path patterns might become long, which makes it less readable. I'd propose that you can use whitespaces / enters to add extra resource path patterns and same can be said for the severity:

<whitelistedResourcePathPatterns>
    /apps/mysite/components/.*,
    /apps/foundation/components/form/.*,
    /apps/fd/af/components/.*,
</whitelistedResourcePathPatterns>

Another improvement would be that you can actually set comments, so something like the following:

<whitelistedResourcePathPatternsArray>
    <!-- Ignored because of reason X -->
    <item>/apps/mysite/components/.*</item>
    <!-- Ignored because of reason Y -->
    <item>/apps/foundation/components/form/.*</item>
    <!-- Ignored because of reason Z -->
    <item>/apps/fd/af/components/.*</item>
</whitelistedResourcePathPatterns>

[kwin]

@royteeuwen PR merged, thanks for the contribution. Can you create a new issue to support the supplying those as individual parameters (so comments are possible).

[royteeuwen]

@kwin I actually tried it out now, and the following pattern seems to be possible:

<whitelistedResourcePathPatterns>
    /apps/mysite/components/.*,  <!-- Ignored because of reason X -->
    /apps/foundation/components/form/.*, <!-- Ignored because of reason Y -->
    /apps/fd/af/components/.*,
</whitelistedResourcePathPatterns>

So this also seems to cover what we need :), didn't expect the validator to strip those