build: use exact versions for integration project dependencies (#33968)

Since we cannot run `yarn install` with the `--frozen-lockfile` option
(because we want to be able to install the locally built Angular
packages), integration project lockfiles are susceptible to getting
out-of-sync with the corresponding `package.json`. When this happens,
yarn will install the latest available version that satisfies the
version range specified in `package.json`.

This commit adds another line of defense, by specifying exact versions
for the dependencies in `package.json` files (i.e. `1.33.7` instead of
`^1.33.0`). While transitive dependencies will be unpinned, this still
ensures that the same version of direct dependencies will be installed
in case of an out-of-sync lockfile, thus reducing the probability of
random failures.

PR Close #33968

integration/ngcc/package.json

@@ -4,7 +4,7 @@
   "license": "MIT",
   "dependencies": {
     "@angular/animations": "file:../../dist/packages-dist/animations",
-    "@angular/cdk": "^8.0.0",
+    "@angular/cdk": "8.0.0",
     "@angular/common": "file:../../dist/packages-dist/common",
     "@angular/compiler": "file:../../dist/packages-dist/compiler",
     "@angular/compiler-cli": "file:../../dist/packages-dist/compiler-cli",

integration/ngcc/yarn.lock

@@ -5,7 +5,7 @@
 "@angular/animations@file:../../dist/packages-dist/animations":
   version "9.0.0-rc.1"
 
-"@angular/cdk@^8.0.0":
+"@angular/cdk@8.0.0":
   version "8.0.0"
   resolved "https://registry.yarnpkg.com/@angular/cdk/-/cdk-8.0.0.tgz#34ca95e71d71780b29b5ba07318c88c4577bdc25"
   integrity sha512-2vsRWEHNARe0iRmqgzvM67gwfRy+aKvdef4Qu9L+ndSsTrrZT3tSgG8SMn1v9SfBHnx5G8mo4d1AMquXG69AuQ==