Each generator should use its own Type instead of BaseApplication

[Tcharl]

Overview of the issue

With the current implementation, it's difficult to add methods on tasks because they are using BaseApplication as input object.

i.e. { application } passed to asPreparingTaskGroup's method of generator-angular is a BaseApplication instead of the generator-angular/types.d.ts#AngularApplication

Same trick could be implemented for Entity (so that an Angular Entity can contain specific attributes and methods, like angularFormPath

Motivation for or Use Case

It would allow more modularity and ease of extension.

• [ ] Checking this box is mandatory (this is just to show you read everything)

[mshima]

It’s quite complicated since there is lots of inter dependencies in main generators. But non application generators types like ci-cd, workspaces needs to be improved.