build: use `pin` instead of `replace` range strategy (#25252)
build: use `pin` instead of `replace` range strategy (#25252)

We always want to pin to the versions we use, and not rely on
version ranges. This is an attempt to fix that the Bazel workspace
file has not been updated.

https://github.com/angular/dev-infra/runs/7289796990?check_suite_focus=true.
angular/components,crisbeto/material2,crisbeto/material2,angular/components,crisbeto/material2,angular/components,angular/components,crisbeto/material2