Updated Google Analytics

* Universal Google Analytics tracking
* Removed CRLF line endings
Add panning behavoir to browser graph results.

Create huge rect to cover whole svg.
Track zoom behavior and move container.
Turn off mousewheel zooming.
Extra nodejs note for Debian/Ubuntu.
Add projectFreshSortExpressions rewriter
Last committed transaction refers to last forcefully appended to log

There was a race condition where
TransactionIdStore#getLastCommittedTransactionId() might return a
transaction id higher than existed in the log on disk, actually even even
before even appended to the log buffer. This resulted in a temporary
condition where a thread would query for last committed transaction id and
then try to retreive those transactions and would fail with an exception
saying that the requested transaction didn't exist.

So this commit introduces a phase before 'committed' which is 'committing'
and those are marked as committed when they have been forcefully committed
to the log. So TransactionIdStore#getLastCommittedTransactionId() method
name is unchanged, but its behaviour is changed to return the last
(highest) truly committed transaction, not the last committing.
Merge pull request #2909 from simpsonjulian/new-google-analytics

Updated Google Analytics
Merge pull request #2956 from tinwelint/2.2-next-and-applied-tx-window

Last committed transaction refers to last forcefully appended to log
Further dismantle inlineProjections

It no longer produces WITH * clauses, the reason being that they
were making it harder for the planner to reason about arguments
that need to be fed into a tail planner query.

Instead, the planner query builder will squash two planner queries
together if the intermediate projection is a simple identifier
to identifier mapping.
Merge pull request #2947 from nigelsmall/readme-tweak-for-ubuntu

Extra nodejs note for Debian/Ubuntu.
No longer closes txId on append failure

since we now distunguish between committing and committed txId. The
appender gets a next committing txId, which is just a candidate for
committing. So in case of failure to append there's no transaction to
close since it's not marked as committed. Marking as committed is the last
operation of appending.

This issue would be observed by having a transaction failing to append to
the log, to the go and shut down the database. The database would await
last closed transaction to be the same as the last committed, and since
last closed would be lastCommitted+1 that would never happen.
Merge pull request #2955 from jakub-/fresh-name-rewriters

Fresh name rewriters
Merge pull request #2963 from tinwelint/2.2-undo-close-on-append-failure

No longer closes txId on append failure
Changes synchronization between LogFile and TransactionAppender

such that transactions cannot be appended and rotated away before properly
applied and closed. TransactionAppender now grabs the same monitor while
appending, as LogFile does when rotating.
More information in AIOOBE
Merge pull request #2965 from tinwelint/2.2-append-and-rotate-control

Changes synchronization between LogFile and TransactionAppender
Merge pull request #2934 from oskarhane/svg_pan

Browser: Add panning behavior to graph results
Merge branch 'master' into rollinglogs