Widen restrictive archive traversal, fixes #1925

[Vogel612]

---

Make sure these boxes are checked before submitting your PR -- thank you!

• Added an entry into CHANGELOG.md if you have changed SpotBugs code

[KengoTODA]

One request I left, please check. And if possible, try to reproduce the issue you want to fix by a unit test.

[Vogel612]

@KengoTODA I have updated the public API as per your request. I am having a hard time finding the existing unit-tests relating to the ClassPathBuilder, though. Could you give me a hint where I should be looking?

[Vogel612]

@KengoTODA I added some unit-tests that rely on a handbuilt nested archive I added to the spotbugsTestCases. I really dislike this setup for the test case, but since I am not familiar enough with the codebase (and there was virtually no documentation on how something like this could even be attempted), that's the hack I went with.

Because these tests require acessing the engine configuration and I didn't want to mess with user preferences between test cases I added an overload to the SpotBugsRule used to integrate the Engine into UnitTests to support modifying the engine in code just before the execution of the actual analysis.

[KengoTODA]

The code is LGTM. Thanks! Add an entry to CHANGELOG.md then I'll merge this PR for the coming release.

[Vogel612]

@KengoTODA Added a changelog entry and rebased onto the master branch. All commits have been squashed into a single one.

[KengoTODA]

Everything LGTM. Thanks a lot! 👍