Fix spurious JSDoc modifier errors on object literal members

[Copilot]

Analysis

In JS files, JSDoc modifier tags like @override, @private, @readonly are reparsed into synthetic modifier nodes on the members they annotate. That's correct for class-like members, but object literal methods and accessors aren't class members, so reparsing modifiers onto them produced spurious grammar errors (TS1042 "modifier cannot be used here" and TS1184 "Modifiers cannot appear here"). Because reparsing happens at parse time, the errors showed up even without checkJs.

Fix

In reparseHosted, skip reparsing JSDoc modifier tags onto method/get/set members when they're being parsed as object literal members (PCObjectLiteralMembers). Class members are unaffected: they still get their modifiers and the usual semantic checks, e.g. @override without a base class still errors.

Tests are consolidated into two cases that vary by @checkJs: true,false to cover both modes from one source file.

[jakebailey]

@copilot Fix the PR description and title to now match the state of this change.

[Copilot]

Pull request overview

This PR fixes a parser-level bug in the TypeScript-Go JSDoc reparser where JSDoc modifier tags (e.g. @override, @readonly) were being converted into synthetic modifiers on object literal methods/accessors, producing spurious grammar diagnostics even when checkJs is off. The change scopes JSDoc-modifier-to-synthetic-modifier reparsing to class-like members, and adds regression coverage.

Changes:

• Update reparseHosted to skip reparsing JSDoc modifier tags onto method/get/set nodes when parsing within PCObjectLiteralMembers.
• Add a compiler regression test covering object literal methods/accessors under @checkJs: true,false.
• Add a companion compiler test ensuring class members still receive JSDoc modifier semantic validation under checkJs.

Reviewed changes

Copilot reviewed 14 out of 14 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
internal/parser/reparser.go	Skips converting JSDoc modifier tags into synthetic modifiers for object literal method/get/set members (prevents spurious grammar errors).
testdata/tests/cases/compiler/jsdocModifiersInObjectLiteral.ts	New regression test ensuring object-literal members with JSDoc modifier tags do not produce grammar errors (both checkJs modes).
testdata/tests/cases/compiler/jsdocModifiersInClass.ts	New regression test ensuring class members still get semantic validation for JSDoc modifiers under checkJs.
`testdata/baselines/reference/compiler/jsdocModifiersInObjectLiteral(checkjs=true	false).*`
`testdata/baselines/reference/compiler/jsdocModifiersInClass(checkjs=true	false).*`