allow specifying ranges in clarifications file and add strict usage checking for them

[ol-teuto]

We had the problem, that clarifications would go quickly out of sync due to automatic dependency updates.

This adds the ability to specify semver ranges in the clarifications file, because usually licenses don't change. Exact versions are still supported, so this shouldn't be a breaking change.

To make sure we don't accidentally miss when a dependency updates and is now out of the specified semver range, this also adds a new option --clarificationsMatchAll (not too sure about the name, other ideas welcome) which causes an error if one or multiple clarifications weren't actually used. This is off by default to keep the current behaviour of not erroring.

[RSeidelsohn]

Thank you so much for your improvement. Actually, I still do not understand the tests which are mostly untouched since I took over (forked) the project - so this is a big construction site for me still. This is why also the clarifications files are still partly a question mark to me.
Hopefully, this will change in the future.
And if you are interested, I would be happy to add you to the repo maintainers! All help is more than welcome, and I really think your last two additions add a lot of value to the project.