Also clean up style a bit. `perl.js` is oddly spaced!

Issue #3015

To fix this I had to introduce new state parameter that tells if
cursor is before colon or not.

Fixes bug #2156 for the most part

indention was bugged because it was reaching a wrong state when
any text that was not in the known set of words or patterns was
incurred.

for eg:
	head
		| <---- cursor should be here

and lets take  color : red as another example
now 'red' is same to the current tokenizer as 'head' from the first
example. So it indents for red automatically.

It was fixed by not letting any text after colon to reach the state
where it appends an indent after it.

Issue #2967

So that => in a string or comment doesn't trigger weird indentation.

Closes #2993

That's what the parser configuration object is for. Also,
I am unsure how this was supposed to even work.

Issue #2996

Also turn off reindentation inside strings and comments.

Issue #2980

Issue #2976

See https://developers.google.com/closure/templates/ for documentation.
Closure Templates support text, HTML, JS and CSS code.

I'm not extremely happy with the indentation which is currently based
just on the Soy tags, not on the underlying code. Although this style
is possible and sometimes used, it's not the most common style.

Completing inside a word used to try and take the whole word into
account. This is not typical completion behavior, and often not what
you want. After this change, the addons only take the part of the
word in front of the cursor into account.

A loop is caused in the Puppet mode when adding a capital letter
due to an incomplete regex match and use of the backUp function.
Resolving this issue required checking for a full match against
the word before calling backUp on the stream.

Issue #2967

Issue #2969

Issue #2967

Remove a bunch of convoluting abstractions, make sure the regexps are
actually cached.

Issue #2964

Closes #2960

Issue #2952

Issue #2928
Issue #2958