Why propose debugging C++ code with `Visual Studio`, but it also works with VS Code?

### Page URL

https://docs.flutter.dev/testing/native-debugging/

### Page source

https://docs.flutter.dev/testing/native-debugging#debug-dart-and-cplusplus-code-using-visual-studio

### Describe the problem

One can easily add a windows process to VS Code, after starting a Flutter app, also in VSCode, just with:

`launch.json`
```
{
"name": "Attach (Windows)",
"type": "cppvsdbg",
"request": "attach",
"processId": "${command:pickProcess}",
}
```

So I would propose to engage using just one IDE (here: VSCode) for developing on Windows instead of proposing to install Visual Studio.

This has the following advantages:
- Using less storage (as no Visual Studio is needed)
- Using less memory during development
- No need to learn multiple IDEs
- Debug in the same IDE (no need to switch between windows and breakpoints)

And no: one doesn't need to install Visual Studio (which requires at minimum than 20GB) vs "Visual Studio Build Tools" only (https://visualstudio.microsoft.com/downloads/#build-tools-for-visual-studio-2022) in order to develop Windows apps.

Search request for "Visual Studio 2022" where we also should engage using only the "Visual Studio Build Tools" instead of the full blown setup (but this might be another topic):
https://github.com/search?q=repo%3Aflutter%2Fwebsite+%22visual+studio+2022%22&type=code

### Expected fix

Engage to use VSCode as default debugging tool for native code instead of "Visual Studio"

### Additional context

I can try to rewrite the docs, but first I want your opinion, if that is something Flutter wants to engage.

### I would like to fix this problem.

- [ ] I will try and fix this problem on docs.flutter.dev.