Update dependencies to avoid unnecessary warnings

We currently get a number of warnings when a new application is installed:

warning ” > @spartacus/storefront@1.0.0" has incorrect peer dependency “@angular/animations@~8.0.0".
warning ” > @spartacus/storefront@1.0.0" has incorrect peer dependency “@angular/common@~8.0.0".
warning ” > @spartacus/storefront@1.0.0" has incorrect peer dependency “@angular/compiler@~8.0.0".
warning ” > @spartacus/storefront@1.0.0" has incorrect peer dependency “@angular/core@~8.0.0".
warning ” > @spartacus/storefront@1.0.0" has incorrect peer dependency “@angular/forms@~8.0.0".
warning ” > @spartacus/storefront@1.0.0" has incorrect peer dependency “@angular/platform-browser@~8.0.0".
warning ” > @spartacus/storefront@1.0.0" has incorrect peer dependency “@angular/platform-browser-dynamic@~8.0.0".
warning ” > @spartacus/storefront@1.0.0" has unmet peer dependency “@angular/pwa@^0.800.2".
warning ” > @spartacus/storefront@1.0.0" has incorrect peer dependency “@angular/router@~8.0.0".
warning ” > @spartacus/storefront@1.0.0" has unmet peer dependency “@angular/service-worker@~8.0.0".
warning ” > @spartacus/storefront@1.0.0" has unmet peer dependency “@ng-bootstrap/ng-bootstrap@4.1.0".
warning ” > @spartacus/storefront@1.0.0" has unmet peer dependency “@ng-select/ng-select@^2.13.2".
warning ” > @spartacus/storefront@1.0.0" has unmet peer dependency “@ngrx/effects@~8.0.1".
warning ” > @spartacus/storefront@1.0.0" has unmet peer dependency “@ngrx/router-store@~8.0.1".
warning ” > @spartacus/storefront@1.0.0" has unmet peer dependency “@ngrx/store@~8.0.1".
warning ” > @spartacus/storefront@1.0.0" has unmet peer dependency “@spartacus/core@latest”.
warning ” > @spartacus/storefront@1.0.0" has unmet peer dependency “@spartacus/styles@latest”.
warning ” > @spartacus/storefront@1.0.0" has unmet peer dependency “bootstrap@^4.2.1".
warning ” > @spartacus/storefront@1.0.0" has unmet peer dependency “core-js@^2.5.7”.

Having those warning indicates that we are providing too strict dependencies for no good reason. It would mean whenever a new dependency becomes available (and used when generating a new app using a later version angular-cli), new warnings will popup. We should improve the dependencies so that the these warnings will not show up. The key thing to do here is to add the major version with a caret (^), so that the latest minor and patch release will be used. On top of that, we should depend on the latest minor we like to use.

Task: Change spartacus dependencies:

Change @angular/animations@~8.0.0 to @angular/animations@^8.0.0
Change @angular/common@~8.0.0 to @angular/common@^8.0.0
Change @angular/compiler@~8.0.0 to @angular/compiler@^8.0.0
Change @angular/core@~8.0.0 to @angular/core@^8.0.0
Change @angular/forms@~8.0.0 to @angular/forms@^8.0.0
Change @angular/platform-browser@~8.0.0 to @angular/platform-browser@^8.0.0
Change @angular/platform-browser-dynamic@~8.0.0 to @angular/platform-browser-dynamic@^8.0.0
Change @angular/pwa@^0.800.2 to ???
Change @angular/router@~8.0.0 to @angular/router@^8.0.0
Change @angular/service-worker@~8.0.0 to @angular/service-worker@^8.0.0
Change @angular/ng-bootstrap@~8.0.0 to @angular/ng-bootstrap@^8.0.0
Change @angular/ng-select@^2.13.2 to ???
Change @ngrx/effects@~8.0.1 to @ngrx/effects@^8.0.0
Change @ngrx/router-store@~8.0.1 to @ngrx/router-store@^8.0.0
Change @ngrx/store@~8.0.1 to @ngrx/store@^8.0.0
Change @ngrx/effects@~8.0.1 to @ngrx/effects@^8.0.0
Change @spartacus/core@latest to @ngrx/effects@^8.0.0
Change @spartacus/styles@latest to @ngrx/effects@^8.0.0
Change bootstrap@^4.2.1 to ???
Change core-js@^2.5.7 to ???

The questionmarks indicate that i'm not sure how we fix those, please investigate.

SAP / spartacus

Update dependencies to avoid unnecessary warnings #3601