Move the old Comments controller aside and write a new simpler one
that for now only manages the comments index page.

Had gone missing with some previous refactoring.

Comments get rendered through the comments.List view.

Change Docs.Application to initialize comments before anything else.
This way the rest of the app can rely on comment counts to be
already loaded and avoid setting up listeners all over the place.

Additionally the CommentCounts is now accessed through Docs.Comments
and never directly as it's no more a singleton.

The Docs.Auth is now observable and fires an "initialized" event
after it's been set up.

Created Docs.Auth which performs the actual login/logout stuff.
Docs.view.auth.Form represents the form at the header of the app,
firering "login" and "logout" events.

The Auth controller just binds these two things together - listening
to the events from AuthForm, performing the login with Docs.Auth
and calling back to AuthForm to change how it looks after login.

Didn't really succeed fully as other stuff in Comments controller
also depends on calling the openComments and closeComments methods.

Crap.

Forgot to rename selector in controller.

This will take care of rendering the comments expander together with a
large heading "Comments".  Use in the main comments section of class
and in guides and videos.

Move the rendering of class comment counts into cls.Overview class
plus those new classes.

Access user properties as subproperties of user.

The form now determines by itself whether to show the definedIn
info or not.

Moved bunch of code away from the humongous Docs.view.Comments.

The emailHash of user wasn't sent when user logged in.

Add note about replying to other people.

Attempt making the syntax help more visible.

Add a new version with a different name alongside it.

This way we can keep two versions of the API working at the same time,
which is needed when first deploying the backend code and then waiting
for the frontend code to get moved into live.

Added field to the top of both users and topics which allows filtering
the lists below them.

Every time the filtering happens, the previously existing selection is
cleared.  This is maybe not the best behavior, but that's the compromise
I arrived at to prevent several edge-case bugs.  The problem is, that
when you filter out a currently selected record, it becomes deselected,
but the deselect event doesn't fire to let us know...

Only remember the sorting order of comments page until next browser
refresh.

Now only the hideRead is remembered across sessions (and that's a
moderator-only setting).

Settle to a nice camelCased naming scheme.

Replacing the magic color value scattered around in code.

Created HeaderMenu class that provides the UI for switching.
Allow only user or topic to be selected (not both together).

For start show the list in place of users list.