[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
Jep.
We just need to come together what your naming have in common with mine ;-)

When i say:
- `parent` this would just try to create a Route for a possible parent route like /news/falsy-news-name would create a route to /news when it exits (-> collection with one route)
- `ancestor` this would create a collection of Routes of all possible ancestors like /news/falsy-news-name would create a list of all children of /news

Maybe now you know what i mean with "asking for some help with the QueryBuilder". parent is easy, but the others means some "join-action".

@dbu What would you like to add as custom `Matcher`?