Use the request URI as the cache key instead of the template name

I've been using your module in an app with multiple static pages, but all of them can be internationalized.
If I enable caching, the content of the first of the languages is cached and returned for any of the other languages.
Since I set the language in the route, I changed the caching system so that the complete route is used instead of the template name, this way multiple routes with the same template can have separate cache items.
Indeed I think it makes sense to cache each resource by itself, since the route identifies each resource uniquely.

What do you think @weierophinney