RFC: ES6 container

[RFC document](https://github.com/MajorBreakfast/rfcs/blob/master/active/0000-es6-container.md)
> Maybe the template could have the respective routes it links to as dependencies

this is problematic, as routes can depend on other things. Thereby retaining more then expected.

The proposed solution is to extract the deserialize/serialize part of routes into there own entities and strongly encourage those have no dependencies themselves. This way those can exist based on either template retention or just keep them around globally