Support multiple backend configurations

Right now, the only supported configuration has to be called "xwiki", because it's the first segment of the URL when accessing the Cristal resource handler. We need a mechanism to support other names, no matter where the Cristal resource is accessed on XWiki.