build: update tooling to use new entry-point for dev-infra exports (#45206)

Previously, dev-infra only bundled the CLI with all its dependencies, while
we still also kept all bundled dependencies in the `dependencies`. This basically
meant that the CLI bundling did not provide any value at all.

We fixed this upstream and now dependencies are still bundled, but no longer
also declared as `dependencies`. We also stopped shipping deep JS files, only
shipping the bundles now.

As part of this deep file removal, we introduced a runtime entry-point for
exports/types. This one will also benefit from the bundling and it will be
predictable what symbols dev-infra consumer projects rely on (allowing us to
also have an API guard or something in the future).

PR Close #45206

.ng-dev/pullRequest.ts

@@ -1,4 +1,4 @@
-import {PullRequestConfig} from '@angular/dev-infra-private/ng-dev/pr/config';
+import {PullRequestConfig} from '@angular/dev-infra-private/ng-dev';
 
 /**
  * Configuration for the merge tool in `ng-dev`. This sets up the labels which
@@ -19,5 +19,5 @@ export const pullRequest: PullRequestConfig = {
   // `dev-infra` and `docs-infra` are not affecting the public NPM packages. Similarly,
   // the `bazel` package is not considered part of the public API so that features
   // can land in patch branches.
-  targetLabelExemptScopes: ['dev-infra', 'docs-infra', 'bazel']
+  targetLabelExemptScopes: ['dev-infra', 'docs-infra', 'bazel'],
 };