[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
yeah, i was changing my mind while writing the comment ;-)

so yeah, lets group them. maybe alias is not the best name for that. what about `group`? and have examples like "hierarchy", "search", "currently_hot"...