implement code fix for override of js files

[stkevintan]

Based on Kingwl#8
Fixes #39669

cc @sandersn @Kingwl

[typescript-bot]

This PR doesn't have any linked issues. Please open an issue that references this PR. From there we can discuss and prioritise.

[sandersn]

@stkevintan If you're going to take this over from @Kingwl, can you

1. Address the comments I made on Override codefix in js Kingwl/TypeScript#8
2. Amend the commit to add Kingwl as a co-author. (Probably requires a force push, not a literal amend)

[stkevintan]

Hi, @sandersn Sorry for the delay, I was on-call last weeks.
basically, I almost did what you've comment, but I am not sure your question on the emitter.ts, as I understand, if we don't emit the override/public tags, tsc will report errors when noImplicitOverride : true on the override methods according to #45656

[sandersn]

I think it's fine to emit the comments, I just wondered why they changed from no-ops to emits.
However, I don't think tsc will report errors on emitted code because it shouldn't be checking emitted code at all.

[sandersn]

Just waiting on an emit test now.

[sandersn]

Noticed a couple more minor things. Otherwise looking good.

[sandersn]

Tests still fail -- a couple of failures from the new tests and 5 more from existing tests.

[stkevintan]

Tests still fail -- a couple of failures from the new tests and 5 more from existing tests.

Hi， @sandersn sorry for the delay. Just figure out the diagnostic messages have been improved for JS files in my previous #45656. so just wondering: is it necessary to specify a different descriptions of code fix action for js files as well ?

PS: could you please help rerun the browser integration test ? it seems it failed with a transient error.

[Kingwl]

Congrats @stkevintan !

Photograph looks handsome! @sandersn 😉