fix(@schematics/angular): add module option in library tsconfig

[alan-agius4]

When not specified the commonjs will be used which will cause erros when consuming the library Module not found: Error: Can't resolve ' commonjs-proxy:../file

ng-packagr/ng-packagr#944 (comment)

Closes: #11255

//cc @filipesilva

[devoto13]

tsconfig.lib.json extends tsconfig.json, where module is set to es2015.

I think this is a regression from #11196. It moved the module property from multiple places to only tsconfig.json. It should work perfectly fine in the newly generated CLI workspaces. The problem is that existing workspaces don't have module: "es2015" in the root tsconfig.json and therefore generating new lib project in the existing workspace leads to the above error.

PS I suspect that generating new application in the existing workspace will have similar problem.

[alan-agius4]

Yes indeed it's a regression from that PR, not sure how to proceed.

[alan-agius4]

Shall we add this in the migration similar to this?
#11261

[angular-automatic-lock-bot]

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}