[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
But i would leave a `alias` attribute in the tag-setting for getting them sorted, right? So the developer for the template can fetch the the information from `best_matches.{alias-name}`