LSP big_file_edits performance regression

[ry]

It seems this happened in 728d205

cc @kitsonk @dsherret @jeanp413

[kitsonk]

The code actions needs a deeper refactor anyways. I will take a look.

[kitsonk]

This will be resolved (and improved) by #12535

[kitsonk]

In #11555 we added a significant feature, with especially big files, requires additional calls into tsc to see what code actions are applicable, so we cannot totally offset the impact of this. #12535 did improve some of the performance regression (and improved a baseline not related to just code actions in big files):

The biggest opportunity for performance improvement now is to not use tsc to calculate the "NavigationTree" but instead calculate this in swc. The navigation tree is essentially a simplified AST which is used by vscode in several situations (like syntax highlighting) and is "costly" for tsc to generate (as well as it being a large JSON structure we have to op out of the tsc isolate). This is covered by #11032.

I am going to close this, and we can figure out the priority for #11032.