develop, run, debug in VSCode

[nemesure]

Checklist

• Testing:

  • The feature has automated tests
  • Tests were run
  • If not, explain how you tested your changes

• Documentation:

  • The feature is documented
  • The documentation is up to date
  • Release notes:
    • Added an entry if the change is breaking or significant
    • Added an entry when adding a new feature

[georgweiss]

The master branch is now on Java 25, so references to "JDK 21" should be updated.

[jacomago]

I would prefer not having ide settings inside development repos, I find they get stale fast and can become OS specific. Better IMHO to add them to the gitignore files.

[georgweiss]

Agree with @jacomago

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud

[shroffk]

Thanks @nemesure for expanding the documentation with support for VSCode

I see that the .vscode files you are including are generic enough that currently they should be useful for anyone... however, I am afraid that we might open the pandora's box for other IDEs ( which don't have such clean internal files... like eclipse and idea )...so for now maybe we can skip these

I think the documentation for VSCode usage is good enough that generating these files should happen automatically