Update LKG
Revert unintended change to MutationObserver constructor signature from 5946ba0cdc45
Update LKG
Change version to 1.0.1
Update LKG
Update spec
Bring parser expression parsing in line with the ES5 spec.

Previously, the expression parser contained a single method for parsing binary, conditional and
assignment expressions.  While this simplified things, it led to certain bugs going noticed in
expression parsing.  For example, the following was previously allowed by the parser:

    var a = () => {} || b;

This is not allowed because an arrow function is actually at the same precedence as an assignment
expression.  And, the left side of a logical or expression doesn't allow that precedence.

This change splits out the parsing code to handle the lowest precedence comma expressions, then
then assignment expresssion, then normal binary expressions.  Assignment expressions are called
out specially because (while they look like binary expressions) the grammar rules for them are
particularly different.

Lots of comments have also been added at many points to make it clear how parsing is supposed to
work, and how it maps to the ES5 grammar and the TS extensions.
Merge branch 'release-1.0.1' into release-1.0
Merge branch 'release-1.0' into release-1.0.1
Revert merge of release-1.0.1
Change string index to .charAt in LanguageService.hasAnyUpperCaseCharacter
Redo merge of release-1.0.1
Fix test baseline
Merge branch 'release-1.0' into develop
Fix the crash when the constructor signature from base is not resolved and is used to instantiate another signature
Update LKG
Merge remote-tracking branch 'origin/release-1.0.1' into develop
Improve error baseline reporting
Use tsc.js-style error messages in error baselines