[Feature] Add group_unhandled_paths Option to Enhance filter_unhandled_paths Functionality #91

[piotrhyzy]

PR Title: Add group_unhandled_paths Option to Enhance filter_unhandled_paths Functionality

Hello @stephenhillier and @Filipoliko,

Following the discussion in the previous PR and the suggestions made, I have created an alternative PR (based on @Filipoliko solution) for handling unhandled paths.

Overview of the Changes:

• Introduced the group_unhandled_paths option.
• group_unhandled_paths: Similar to filter_unhandled_paths, but instead of ignoring the requests, they are grouped under the __unknown__ path. This option overrides filter_unhandled_paths by setting it to False. The default value is False.

Reasoning:

• This approach simplifies configuration by linking the two options, reducing potential user confusion.
• Ensures clear intent when configuring the handling of unhandled paths.
• Aligns with the feedback suggesting that group_unhandled_paths provides clear intend even if filter_unhandled_paths is enabled and simply it overrides it.

I believe this solution addresses the concerns raised about having mutually exclusive options and makes the configuration more intuitive.

Please review this alternative approach and let me know your thoughts.

[stephenhillier]

Looks great. I agree with your comments on the two options, having group_unhandled_paths override makes sense to me.

One thing I would say is that users who only set group_unhandled_paths will see the warning, even if they didn't intentionally set filter_unhandled_paths (since it defaults to True). That's a minor issue and we can always adjust the warning later if needed.

[stephenhillier]

Thanks for the update, looks good.