Allow users to pass along stitcher configuration

[hendrikvanantwerpen]

Path stitching can be configured to enable or disable similar path detection. It can be interesting to disable that if the rules allow it, for increased performance. However, for rules that do not allow it, it can lead to exponential blowup.

The path stitcher is often not created by callers directly, but indirectly when e.g. running tests, or running a query. Callers should be able to pass along stitcher parameters to configure the stitcher correctly.

Additionally, language configurations should have an additional value specifying the required stitching parameters for that language. (Ideally these could also be read from package.json for dynamically loaded languages.)