Fix checkGrammarForInvalidDynamicName

[Andarist]

fixes #983

[Copilot]

Pull Request Overview

This PR fixes the behavior of checkGrammarForInvalidDynamicName by inverting the condition that determines when to trigger a grammar error, and updates several baseline error outputs accordingly.

• In grammarchecks.go, the condition is inverted to correctly handle dynamic names.
• Multiple test baseline error files were updated to reflect the corrected error messages.

Reviewed Changes

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

Show a summary per file

File	Description
testdata/baselines/reference/submodule/compiler/overloadsWithComputedNames.errors.txt	Baseline error count reduced and updated error messages.
testdata/baselines/reference/submodule/compiler/isolatedDeclarationErrorsClasses.errors.txt*	Updated error message baselines for computed property name issues.
testdata/baselines/reference/submodule/compiler/indexWithoutParamType2.errors.txt*	Updated error message baselines.
testdata/baselines/reference/submodule/compiler/indexSignatureMustHaveTypeAnnotation.errors.txt*	Updated error message baselines.
testdata/baselines/reference/submodule/compiler/decoratorsOnComputedProperties.errors.txt*	Updated error message baselines related to decorators and computed properties.
testdata/baselines/reference/submodule/compiler/declarationEmit*	Baseline updates for declaration emit errors.
testdata/baselines/reference/submodule/compiler/complicatedPrivacy.errors.txt*	Baseline update for complicated privacy errors.
testdata/baselines/reference/submodule/compiler/capturedParametersInInitializers2.errors.txt*	Baseline update for captured parameter errors.
internal/checker/grammarchecks.go	Fixed logic in checkGrammarForInvalidDynamicName to correctly handle dynamic names.

(* Asterisk indicates multiple related baseline diff files.)

Comments suppressed due to low confidence (1)

internal/checker/grammarchecks.go:1422

• Consider adding an inline comment to explain the inversion of this condition, clarifying that grammar errors should only be triggered for nodes that are bindable dynamic names. This will aid future maintainers in understanding the purpose of the change.

if !c.isNonBindableDynamicName(node) {