Paths for custom JAR files

[justinstroudbah]

Is your feature request related to a problem? Please describe.
If a workspace settings file has path delimiters that are at odds with the client operating system, PMD execution fails and not in a graceful manner. PMD has (historically) been terrible at reporting issues with the rulesets, and this is in that bucket. The error initially leads one to believe that there is a problem with the JAR files specified in the extensions settings.

Describe the solution you'd like
The config class (I think it's called that) should be aware of the granular type of the information it is ingesting. For example, since this is a path it should know the context and validate the setting accordingly. We discovered this because our codebase had a workspace file that was generated in a Windows environment. I realize this is kind of an edge case, but I'm happy to contribute if there is a lack of time and/or resources.

Additional context
It took quite a bit to track this issue down: The reporting person was on a Mac. I was on a Windows 11 box. I had to switch to Debian on WSL to replicate the issue (thank god for WSL.)