Bumping them for every release just adds too much git
noise and history blowup.

Closes #1460

(->> 'clojure.core ns-publics (map first) sort (clojure.string/join " "))

As spotted by the extended linter.

Closes #782

Correct highlighting for the following code snippet should highlight the + as an operator, and each 2 as a number (taken from http://clojuredocs.org/clojure_core/1.2.0/clojure.test/deftest)

    (is (= 4 (+ 2 2)))

Closes #776

Closes #753

Closes #446

I've differentiated between control-structury things and builtins. While there
is rarely a true difference in these things because of the way Clojure works,
it makes sense to highlight them differently. All of the desktop editors make similar
decisions with their Clojure lexers. My reason for doing it is that it allows
for more complex highlighting. I'm not sure if all of the things in the keyword
list make sense there, but they do at a glance. I'll look more closely when I
get to using this and send another pull request with any tweaks.

Clojure's keywords (like :foo) were being highlighted as tags. That doesn't make sense and is
inconsistent with, for example, the Ruby mode. You don't want to highlight tags
the same as keywords in some cases because you can end up with pretty keywords
and hideous HTML tags. I've switched those to be highlighted as atoms as per
the Ruby mode.

A few of the indent words were not being detected because they were being
concatenated without trailing spaces. I fixed that.

Since v2 is the canonical CodeMirror at this point

So that I can put other doc-related stuff there without polluting the
root dir.

It's tiny anyway, no need to force people to include yet another file.

Signed-off-by: Jan Keromnes <janx@linux.com>