Update to angular 11

Is your feature request related to a problem? Please describe. @angular-builders/jest and @angular-builders/custom-webpack should work with Angular 11

Describe the solution you’d like Support Angular 11

Describe alternatives you’ve considered None

Additional context I am currently working on fixing the failing dependabot PRs #870 #871 and #872 and will provide a PR shortly.

@just-jeb you might also want to create a new 10.x.x branch for the Angular 10 release.

[just-jeb]

I’ll take your suggestion into consideration and update the README in order to emphasize the importance of versions alignment. Adding peer dependencies would be wrong in my opinion, since it suggests that you have to explicitly install all the dependencies while you don’t (and it wouldn’t really help if you did).
I understand that upgrading to a beta version is not the best solution you could wish for, but it’s all you’ve got unfortunately.
Stable version will be released after breaking change from #819 is implemented, which, in turn, blocked by this PR and this issue in webpack-merge.
That being said this is the only breaking change expected in v11 so for now the beta version is safe to use.

[mshima]

@just-jeb we recently migrated jhipster to angular 11, but there is a discussion about if we should upgrade @angular-builders to 11 beta.

From my point of view:

• should be mandatory to match @angular-builders/custom-webpack and angular version. So @angular-builders/custom-webpack@^10 should be forbidden to work with angular@^11.
• @angular-builders should be considered a plugin of @angular/cli

If that’s true, @angular-builders should have peer dependencies instead of hard dependencies on @angular-devkit and @angular/cli. For reference see https://nodejs.org/en/blog/npm/peer-dependencies/

Whats your opinion?