Aligning synced vscode sources between vscode/vscode-copilot-chat

[roblourens]

I had issues syncing vscode sources into the chat extension (see https://github.com/microsoft/vscode-copilot-chat/blob/main/CONTRIBUTING.md#use-basecommon-utils) due to some differences in the core/edits files.

The PR is at microsoft/vscode-copilot-chat#518. I made some manual edits here

• microsoft/vscode-copilot-chat@4b82e6b to avoid some type errors that I couldn't figure out how to resolve
• microsoft/vscode-copilot-chat@2108e21 to hook up this ensureDependenciesAreSet function

Then after that, I still have some vitest failures, I think because there used to be a JSON.stringify here https://github.com/microsoft/vscode-copilot-chat/blob/2108e213b9019dcb9616ae16e93763e31d30f478/src/util/vs/editor/common/core/edits/stringEdit.ts#L204.

Could you look at these? I'm also not sure what other manual changes might have been made that might be missing but not causing build or test failures. I'd really like to get back to a place where we can do a clean run of copySources.ts to keep things in sync.

(I also am working through this issue #260650, there are currently more manual edits in the PR branch for that)

[benibenj]

@hediet can you verify the manual edits and look at the test failures, they seem simple. Probably related to your recent edits data structure migrations

[hediet]

I verified the two comments and fixed the vitest failures. Thanks for syncing the source!
I do believe though this is a tooling issue.

[roblourens]

Thank you!

I do believe though this is a tooling issue.

What do you mean by that?

[roblourens]

Actually this isn't complete @hediet, the branch still has manual edits that I added while trying to get it to build

• microsoft/vscode-copilot-chat@4b82e6b to avoid some type errors that I couldn't figure out how to resolve
• microsoft/vscode-copilot-chat@2108e21 to hook up this ensureDependenciesAreSet function

You can revert them manually or you can run npx tsx ./script/setup/copySources.ts to sync it with the latest from the vscode repo (and ignore the other manual changes that I currently have for #260650)