Normalize URLs

[xi]

We use URLs to identify resources and we expect them to unambiguous. But we do not normalize them. So for example we might have //example.com/adhocracy in one place and //example.com/adhocracy/ in another and //example.com//adhocracy in a third. This is bad for caching and webSocket subscriptions because we might duplicate work.