[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
mhhh ... would make sense.

But atm i have got an automatic activation for those `BestMatchers`. 
Just add a tag and yeaaa they are asked for the routes they wanna show.

On the one hand i think, that idea would give one responsibility to much 
to the `BestMatchers` and on the other hand, would should i do with a 
chain of `BestMatcher`.

I could imagine a block like system of a master template and children, 
what do you think @dbu?

Would mean:
- each `BestMatcher` would get  a `getTemplate()` method
- asked for their routes
- asked for its template
- presentation would merge that together