Fix bug: parser fails to parse expressions properly when newline precedes comma

There was an unnecessary semicolon insertion check in parseExpressionInt in
the JS Parser that caused it to fail on the following code
  (function () {
    return 1
        , 2;
  })

[Jasvir, 2009-01-27 02:08:34]

http://codereview.appspot.com/11987/diff/1/3
File src/com/google/caja/parser/js/Parser.java (right):

http://codereview.appspot.com/11987/diff/1/3#newcode698
Line 698: // Handle comma operator
Please add a comment to explain what insertionProtected (at the top of the file
perhaps) - its purpose is highly non-obvious.

[MikeSamuel, 2009-01-27 02:22:59]

http://codereview.appspot.com/11987/diff/1/3
File src/com/google/caja/parser/js/Parser.java (right):

http://codereview.appspot.com/11987/diff/1/3#newcode698
Line 698: // Handle comma operator
On 2009/01/27 02:08:34, jasvir wrote:
> Please add a comment to explain what insertionProtected (at the top of the
file
> perhaps) - its purpose is highly non-obvious.

Done.

[Jasvir, 2009-01-27 05:30:04]

LGTM

(Thank you for the comprehensive ParserTests.  The parser is very complicated -
I believe this CL is correct primarily because of the tests)

[MikeSamuel, 2009-01-27 05:48:23]

@3210