Otter generators evolution

[mrednic-1A]

Modularity

Remove @ngrx deps from the default generators (create + ng g app + ng g lib)

The idea is to check which packages are bringing the @ngrx dependencies and see if the features adding @ngrx present in initial generation is really needed at the beginning or it can be a specific generator.

1. First finding

When generating an app: @o3r/core -> @o3r/application -> @o3r/routing
@o3r/routing needs @ngrx for the routing-guard store -> the routing-guard store can be added by a specific generator if needed (after the creation of the app)

2. TBC

Fixes

1. [Bug]: o3r create + ng g app #2593
2. Error in the logs for the command to display all the generators (npm exec ng g [--] --help)
3. Warning on npm workspace not installed (2 times if we answer yes for telemetry)
4. when logging the list of generators at the end of create, add a differentiator for otter generators from the angular ones (with a link to the doc if possible)
5. @o3r/testing added by default when generating a library
6. [Bug]: Generating an app/lib with a scope leads to unexpected behaviour #2627

[malek-benazzouz]

Hello, I cannot edit the post for now, but I started creating some issues, I have a list with more issues, that I will create when I am back from holidays:

• [Bug]: Generating an app/lib with a scope leads to unexpected behaviour · Issue #2627 · AmadeusITGroup/otter

• [Bug]: Unexpected backslash in angular.json file outputPath when generating an application · Issue #2630 · AmadeusITGroup/otter

• [Feature]: @o3r/create should generate end-of-line LF config · Issue #2628 · AmadeusITGroup/otter

• [Feature]: @o3r/create should handle dependency harmonization in mono-repos · Issue #2629 · AmadeusITGroup/otter