Studio Support for Content Libraries (SOL-1, SOL-2, & SOL-3)

@antoviaque @explorerleslie @cahrens

**Background**: This is the UI code to enable creation and editing of [Content Libraries](https://openedx.atlassian.net/wiki/display/SOL/Content+Libraries). Together with #6033, it implements SOL-1, SOL-2, and SOL-3. Once #6033 has been merged to master, this branch is to be merged to `content-libraries`, which will become the new feature branch for library support.

**Discussion**: Architecture discussed extensively on [the wiki](https://openedx.atlassian.net/wiki/display/SOL/Content+Libraries) and in meetings, then the revised proposal was presented to the [Arch Council](https://openedx.atlassian.net/wiki/display/AC/Architecture+Council) on Oct. 21 and given thumbs up.

**Partner information**: 3rd party-hosted open edX instance, for an edX solutions client.

**Merge deadline**: ASAP - several other PRs are ready and blocking on this.

**Dependencies**: Requires #6033.
@andy-armstrong @bradenmacdonald If it's only purpose is to instantiate `XBlockContainerPage` so that it works with `LibraryContainer` - it should be pretty trivial. On the other hand, it might make sense to perform more aggressive refactoring and make `Container` or `LibraryContainer` got injected into `XBlockContainerPage`. So it depends on what are we trying to achieve and how much effort we can put now.

All in all, if it's only for future extensibility - `LibraryFactory` would be pretty trivial to create.

One question though: are there any tests for `ContainerFactory`? Those should be at least duplicated for `LibraryFactory`.