keep devon4net Cobigen Guide close to the Devon IDE

[quantumfate]

Expected behavior

As a developer, I want to be able to use the Devon IDE to generate my boilerplate code with Cobigen by following the devon4net Cobigen Guide. This would reduce the amount of documentation to be maintained and it facilitates the project generation.

Actual behavior

The devon4net Cobigen Guide instructs the user to install the dotnet sdk and vscode separately from the Devon IDE. This adds an unnecessary step to the guide and the developer will eventually run into issues that will lead to confusion because everything takes place in different locations. Take a look at my comment in this isse for more information.

[JosepFe]

The documentation about using the templates that cobigen uses to generate files on devon4net has been modified.

A new pull request has been opened with these changes, when approved and merged with the main cobigen branch the problem will be fixed. PR link: https://github.com/devonfw/cobigen/pull/1621