build: fix e2e tests failing due to chromedriver release (#14461)

Apparently the webdriver-manager always uses the _latest_ version of the chromedriver. This is problematic because the CI does not always use the latest chrome version that _works_ with the chromedriver from `webdriver-manager`.

In order to fix this, we lock the webdriver manager version to a specific version. Similarly to how it's done for `angular/angular`.

Note that this also restricts which Chrome versions can be run locally with the e2e tests, but the chromedriver range seems to always cover at least the latest two versions (which works for us)

package.json

@@ -56,7 +56,6 @@
     "@bazel/ibazel": "^0.9.0",
     "@bazel/karma": "0.21.0",
     "@bazel/typescript": "0.21.0",
-    "@firebase/app-types": "^0.3.2",
     "@octokit/rest": "^15.9.4",
     "@schematics/angular": "^7.1.2",
     "@types/browser-sync": "^0.0.42",
@@ -83,7 +82,6 @@
     "conventional-changelog": "^3.0.5",
     "dgeni": "^0.4.10",
     "dgeni-packages": "^0.26.12",
-    "firebase": "^5.5.2",
     "firebase-tools": "^4.1.0",
     "fs-extra": "^3.0.1",
     "glob": "^7.1.2",