Clarify error message when an accessor is invoked.

[krk]

Fixes #24554

[RyanCavanaugh]

We like the idea of a better error experience here, but would need a simpler implementation to proceed (maybe a few lines of code). Certainly modifying getImmediateAliasedSymbol is too much risk for the sake of an error message improvement. A less comprehensive check like "Is the valueDeclaration of the property access expression a getter?" (which wouldn't handle 100.0% of cases, but would be much simpler) would be our preferred approach here. Thanks!

[sandersn]

I'm cleaning up our PR backlog, so I'm going to close this one since it's been stale for a while.

@krk feel free to open a new PR addressing #24554. I'd recommend changing the check... functions, maybe checkPropertyAccessExpression and checkElementAccessExpression.