Upgrade to angular 11

[HaoK]

Fixes #14076

Open issues to follow up on:

Angular:
ng run test - fails due to office tabs popping up
npm run build:ssr - fails with "Schema validation failed with the following errors:
Data path "" should NOT have additional properties(vendorChunk)."

[HaoK]

@javiercn I hand ported the initial changes back to the templates

[javiercn]

@HaoK this looks great, does it cover the auth options?

[HaoK]

No I will do that now, and do another port, were there any differences between individual/b2c that I need to look out for? Is one a superset?

[HaoK]

Oh never mind, looks like there's only individual auth option for spa

[javiercn]

Things look good to me so far,

I think we'll have to check the generated templates to understand if there's anything that needs to be updated.

It would be great if you can generate a couple of versions of the templates (no auth and auth) and push them to a repo so that we can play with them a bit.

[HaoK]

https://github.com/HaoK/Random/tree/haok/temp/angular6 and https://github.com/HaoK/Random/tree/haok/temp/angular6ind
are the outputs of the template I just built, the spa client apps seem to run fine, but I see some weird errors when running the whole app via dotnet run, maybe due to package restore/version issues since its looking for SpaProxy6.0.0-dev

[javiercn]

https://github.com/HaoK/Random/tree/haok/temp/angular6 and https://github.com/HaoK/Random/tree/haok/temp/angular6ind
are the outputs of the template I just built, the spa client apps seem to run fine, but I see some weird errors when running the whole app via dotnet run, maybe due to package restore/version issues since its looking for SpaProxy6.0.0-dev

Let me give this a try tomorrow. I can just remove the proxy and start things manually.

[javiercn]

Looks great!