[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:
* [ ] implement the `create()` methods of the base matcher i created (parent, ancestor)
* [ ] bring the `BestMatcherPresentation` to use the custom exception.html.twig i created
* [ ] test for `BestMatcherPresentation`
* [ ] tests for both base matcher
* [ ] finish frontend test by crawling for some given stuff
as i see, its all up to the user what he needs. but to me parent or all anchestors in the tree are both about hierarchy. parent is just a special case. and some system might have another concept of hierarchies (if the first url segment denotes a tag for example, it would be stuff with the same tag).

for the tree hierarchy, you can just split on `/`, have a look at https://github.com/symfony-cmf/Routing/blob/master/Candidates/Candidates.php#L129