[WIP] Create custom behavior for RouteNotFoundException

| Q             | A
| ------------- | ---
| Bug fix?      | no
| New feature?  | yes
| BC breaks?    | no
| Deprecations? | no
| Tests pass?   | no
| Fixed tickets | #10
| License       | MIT
| Doc PR        | need to be done

Todo:
* [x] implement the `create()` methods of the base matcher i created (parent, ancestor)
* [ ] bring the `BestMatcherPresentation` to use the custom exception.html.twig i created
* [x] test for `BestMatcherPresentation`
* [x] tests for both base matcher
* [ ] finish frontend test by crawling for some given stuff
would you not need to build the list of paths with less and less segments until the root? i think right now this is identical with the ParentBestMatcher

what you do below is looking for siblings, not for an anchestor