For classes we now always show the short name in tab title and full
name in tooltip.

For guides/videos/examples the title and tooltip are the same, with
tooltip providing a way to see the title when it's too long to fit
on the tab.

Fixes: #369

We're going to use #shortName also inside Tabs class and want to
share the code. #packageName is a related function and should be
together with #shortName.

Previously it depended on whether you viewed classes by package or
by inheritance.

Mike fixed the server side escaping, so we don't need this hack any more.

Only activate the external guides-search when --search-url option
is used.  Otherwise fall back to old search.

Initial version of the UI - the search results are combined with
API search and shown in the same old dropdown.  This means there
isn't quite enough room to show the full context of full text search
matches and the search is also slower, but it fits nicely to the
current UI.  Plus it was easy to implement.

The most questionable part is how the guide results are placed inside
API search results.  I'm drawing some arbitrary lines between the
scores given by guides search to split the results into boxes like
the API search does.

A new processor to recursively populate the @fires list with events
fired by methods called from a particular method,
and by methods called from there,
etc.

Move common functionality from Fires and MethodCalls to
ScopedTraverser, which provides the ability to loop recursively
through AST tree while keeping track of the variables bound
to `this`.

First off it's just a Js::MethodCalls class that's not yet
connected to JSDuck.

Rewrite the AST-traversing algorithm in a more generic way -
just looping over all the subtrees without having the actual
knowledge of what fields make sense to recurse into.

Looks for this.fireEvent("blah") inside function body.
Also understands me.fireEvent("blah") when me has been
assigned with `this`.

Log warning when unknown event name is used.

For documenting events thrown by a method.

Related to issue: #364

The problem arose from links produced by Marketo which took the
following form:

    http://docs.sencha.com/architect/2-0/?mkt_tok=LONGHASH#!/guide

Now we're stripping all URL parameters after the question mark, leaving
just the path and hash-bang parameters.

Previously the order was pretty-much random.

Leave just small stars behind new classes.  This way it's lot
less cluttered.

The new "New in this version" section covers the details of
what's new much better and doesn't get on the way.

The docs for accessors get auto-generated and we need nothing extra.
Having the :inheritdoc in there also causes errors when looking up
the parent.  For example the following:

    /**
     * @cfg {Number} width
     * @inheritdoc SomeClass#width
     * @accessor
     */

When the accessors would get the @inheritdoc, this would look like
we had the following methods:

    /**
     * @method getWidth
     * @inheritdoc SomeClass#width
     */

    /**
     * @method setWidth
     * @inheritdoc SomeClass#width
     */

But the inheritance system would attempt to inherit the docs from
"width" method, but there is no such thing because we were actually
inheriting from "width" config.

Therefore we're better off without the whole @inheritdoc in accessors.

Related to: #365

Instead of having the class names in headers be the links.

Use the Columns class to do the splitting in exactly the same way
as in Categories.

Let it manage the columns splitting logic so we can also share it
with new items list.