[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
i fear that the type is overcomplicating things here, without the benefit. the user could come up with all kinds of types (i.e. a blog where you search for keywords from the referrer and url, or posts around the same date and so on). i would leave the type out. or if you really think its needed, we should not limit possible types and use `default` if no type is given. then people can use it to group their suggestions. hm, this could make a lot of sense. then the error page can say: "Published around that time:"..., "People are currently looking at:"..., "Search results for *<your google referrer query>*":...