[7.2.x] ivy+docs-infra: compile angular.io with Ivy - #28419

PR Close angular#27954

…ngular#27829)

Currently when building a package on Windows, the typings re-export for secondary entry-points is not valid TypeScript. Similarly the metadata and the "package.json" files use non-posix paths and cause inconsistency within the NPM package.

For example:

_package.json_
```
  "esm5": "./esm5\\core.js",
  "esm2015": "./esm2015\\core.js",
```

_testing.d.t.s_ (of the `core` package)
```
export * from './testing\testing';
```

PR Close angular#27829

…ngular#27829)

PR Close angular#27829

…#27829)

PR Close angular#27829

* Enables the ng_package golden testing on the CI
* Fixes the ng_package golden testing for Windows

PR Close angular#27829

…27915)

* Currently the protractor utils assume that the specified Bazel server runfile can be resolved by just using the real file system. This is not the case on Windows because the runfiles are not symlinked into the working directory and need to be resolved through the runfile manifest.

PR Close angular#27915

Moving the tests over to CircleCI in pretty much "as-is" state just so that we can drop the dependency on Travis.

In the followup changes we plan to migrate these tests to run on sauce under bazel. @gregmagolan is working on that.

I've previously verified that all the tests executed in legacy-unit-tests-local already under bazel.
Therefore the legacy-unit-tests-local job is strictly not necessary any more, but given how flaky legacy-unit-tests-saucelabs is,
it is good to have the -local job just so that we can quickly determine if any failure is a flake or legit issue
(the bazel version of these tests could theoretically run in a slightly different way and fail or not fail in a different way, so having -lcoal job is just an extra safety check).

This change was coauthored with @devversion

PR Close angular#27937

the metadata build seems to be needed only by the offline compiler tests which is currently disabled

PR Close angular#27937

PR Close angular#27937

PR Close angular#27937

we no longer need it... yay!!!

PR Close angular#27937

test.sh is no longer needed... all the tests should now be executed via bazel.

if for whatever reason we need to run the legacy unit test setup, we should should follow the commands that we use to execute those tests in .circle/config.yaml

PR Close angular#27937

this script is now obsolete and not needed any more. yay!!!

PR Close angular#27937

…ode devDep (angular#27937)

I'm not sure why this problem is visible only now or how this worked before, but the CI
is now failing because @types/node is missing.

I also added the yarn.lock file which was previously omitted. We want the yarn.lock file in so that
our deps don't change over time without us knowing.

PR Close angular#27937

PR Close angular#27937

PR Close angular#27937

…ar#27937)

* Groups the two sharded `test_docs_examples` job using CircleCI's `parallelism` feature.  This makes the amount of jobs that show up on a PR, more reduced and also reduces code duplication for maintaining the Circle job definition.

PR Close angular#27937

PR Close angular#27937

…ular#27970)

we missed this one!! oops

the robot should not expect travis status check on PRs any more.

PR Close angular#27970

On push builds, CircleCI provides `CIRCLE_COMPARE_URL`, which we use to
extract the commit range for a given build. When a workflow is rerun
(e.g. to recover from a flaked job), `CIRCLE_COMPARE_URL` is not
defined, causing some jobs to fail.

This commit fixes it by retrieving the compare URL from the original
workflow. It uses a slow process involving a (potentially large) number
of requests to CircleCI API.
It depends on the (undocumented) fact, that the `workspace_id` is the
same on all rerun workflows and the same as the original `workflow_id`.

PR Close angular#27775

we no longer use TravisCI
PR Close angular#27973

…7974)

PR Close angular#27974

PR Close angular#27994

PR Close angular#27997

@alxhub spotted that the public api rule in codeowners is being overriden by the Build & CI Owners rule.

swapping the two sections fixes the problem.

PR Close angular#27999

PR Close angular#27774

the first example at https://angular.io/guide/rx-library,
ReactiveX/rxjs-tslint#7

PR Close angular#27443

This reverts commit 097af5a.
It was accidentally merged on both master and patch branches when
it should have only been merged on master.

The existing example makes it seem like zip is a pipeable operator. It can be used this way, but I think that is for backwards compatibility. You can achieve the same functionality by using it as an Observable creator. I think this also makes the example clearer.

PR Close angular#26790