Use the ~> syntax to allow us to release patches to rkelly-remix
and get the picked up by jsduck installations.

When for-in contains variable declaration, Esprima produced the
whole VariableDeclaration, but RKelly gives just VarDeclNode -
so we wrap it inside a VariabelDeclaration to match Esprima output.

Missing variable in catch clause is a JS syntax error.
This happened to work in old Esprima, but no more works in
neither new Esprima nor RKelly.

That's not supported by RKelly, and really not needed in practice.

It still referenced the old Esprima engine.

Because the EsprimaAdapter gives a string value to regex literals,
which is different from nil received from Esprima itself, we'll
have to check first for regex and after that for string.

Previously && and || were treated as BinaryExpressions, but Esprima
classified these as LogicalExpressions.

The "test" and "body" parts had been switched.

So we don't have to change all the tests that target the old Js::Parser.
Besides, it's better to use a more generic name anyway.

Break the no_doc warning type into three:

- no_doc
- no_doc_member
- no_doc_param

At least in browsers that support it.
Unfortunately Chrome doesn't.

Previously H5 and H6 weren't styled at all, resulting them looking
like plain text.

Also print out message in verbose mode about the auto-detected
config file, so reading it happens with less magic.

Fixes #402

But instead of standard RKelly gem, use our own rkelly-remix fork.

Previously all property keys were treated as being
identifiers - now we correctly detect if they're
strings or numbers.

RKelly chokes when it sees that.

Causes problems with RKelly which chokes when it sees a reserved
word like that inside a property chain.

Ext 1.1 source happened to contained code like:

    /**
     * @param {String} (optional)
     */

which brought JSDuck crashing down.

The Js::Associator expects all nodes to have "range".

Inside RKellyParser:

- Invoke RKelly.
- Adapt its output with RKellyAdapter
- Set the correct range for root node.
- Pass the adapated AST to Associator.

Change RKellyAdapter to:

- Create root "Program" node.
- Adapt the comment nodes inside this root node.
- Adjust the range end by one - so it matches the esprima way.
- Include line number to the adapter range.

Intending to use the same logic in RKellyParser.

In an attempt to replace Esprima with RKelly, I created an adapter
to convert the RKelly AST into Esprima AST.

The backwards-compatibility fix for code like:

    Here's the code example:<pre><code>
    alert("Blah");
    </code></pre>

was a bit too lose.  So tightened it up to only apply in case
where the <pre> or <pre><code> is at the end of line.

Fixes: #380

There was a conflict with one method looping over array while
other deleting items from it at the same time.

Fixes: #378