More extensive check between allowed rules vs. protected rules

[alexAubin]

This is a follow-up of this discussion to try to fix this thing where if you have these settings :

    "protected_urls": [
        "yolo.test/foo", 
        "yolo.test/foo/admin"
    ], 
    "users": {
        "alice": {
            "yolo.test/foo": "Foo Test", 
            "yolo.test/foo/admin": "Foo Test (Admin)"
        }, 
        "bob": {
            "yolo.test/foo": "Foo Test"
        }
    }

then currently bob has access to /foo/admin despite the fact that the intention would be that only alice should ...

This draft allow to perform a more extensive check, and by this I mean checking what's the rule that has the longest match with respect to the requested uri...

This seem to be kinda working but gotta run moar test to validate the thousand of different use case to see that this does not cause any regression

[alexAubin]

So that's kinda working, still would be nice if anybody has feedback if there's a better way to implement this ...

[Josue-T]

For me it look like good. But I didn't a really deep review...

I still just not really like the idea to merge the full url and the "url without the domain".

Maybe there are a better way to do this (maybe as discussed here ) but we still can improve this later. I think it's just some internal change. So it won't impact the apps.