Draft: docs: guide for vscode esp-target setup

[horw]

Description

This article explains how to set up the VSCode environment for correct file navigation across different target.

Checklist

Before submitting a Pull Request, please ensure the following:

• 🚨 This PR does not introduce breaking changes.
• All CI checks (GH Actions) pass.
• Documentation is updated as needed.
• Tests are updated or added as necessary.
• Code is well-commented, especially in complex areas.
• Git history is clean — commits are squashed to the minimum necessary.

[horw]

Still in progress, but overall, it will look like this.
@brianignacio5 @Kainarx Do you have any advice on how to improve it?

[github-actions]

🎉 A preview for this PR is available at: https://preview-developer.espressif.com/pr395/

[brianignacio5]

I consider that having a single build directory is not a good ideas for most users. The c_cpp_properties.json can be defined on each project. The compiler path script could be executed in each project accordingly. You could also define a task in tasks.json to define this update script.

The issue with syntax highlight is that it relies on build files which should be a result of compilation. If you are relying on previous build files from other project it could lead to wrong headers too, since maybe IDF_TARGET is the same but other sdkconfig settings could diverge.

What is the target use case listed here?

How about consider a smaller build step like idf.py reconfigure to generate just the configuration step of CMake which generate compile_commands.json and config/sdkconfig.h