[Bug]: tsconfig.base.json and tsconfig.build.json are not properly generated

[malek-benazzouz]

Package name

core

Package version

11.5.3

Reproduction steps

Create a project with @o3r/create, then generate an app and a lib:

npm create @o3r project
ng g application app
ng g library lib

Current result

• File tsconfig.base.json is not generated.
• File tsconfig.build.json is not generated.
• The app and lib tsconfig files extend ../../tsconfig.json root file.
• In the lib tsconfig.spec.json file, there is a reference to path ./tsconfig.build.composite.json, but this file was not generated.
• The path mapping in tsconfig.json file is not properly configured: the generated path mapping is "lib": ["libs/lib/dist", "libs/lib/src/public-api"], which does not allow for a proper IDE navigation. A proper config could also ease local lib development (today you have to run ng build lib --watch to have your lib changes live reloaded).

Expected result

The generated configuration should be similar to the one of o3r monorepo, with tsconfig.base.json and tsconfig.build.json files generated, and the app and lib properly referencing these files. Path mappings should also be properly configured.

Additional comments

No response

[malek-benazzouz]

Additional note: fixing the path mappings will also fix the following unit test issue, that is raised as soon as we try to call a lib component from the app:

Could not locate module @nevio/library mapped as:  ..\libs\lib\dist,libs\lib\src\public-api

[malek-benazzouz]

To be confirmed:
Today the generated tsconfig.lib.prod.json extends ./tsconfig.lib.json, but the expected behavior is that it should extend ../../tsconfig.build.json instead.