Fix ASI before accessor keyword identifiers

[davejcameron]

Problem

The get/set accessor parser can treat an identifier followed by a statement with a parenthesized head and block body as accessor syntax when a semicolon or line break separates them.

return set;
for (const x of xs) { y(x) }

That should parse as two statements, but the accessor parser can read it as if it were set for (...) { ... } inside the returned expression.

Fix

Reject accessor parsing when a semicolon boundary or line terminator appears between the get/set keyword candidate and the property name. In that case, get/set falls back to the normal identifier path and ASI can split the following statement correctly.

Validation

• Direct parse check for return set; followed by a for block
• node test/jessie.js: 71 tests, 243 assertions