… v14 libraries

Locally-built APF v14 libraries should be resolved properly. Webpack
currently does not resolve them (in e.g. `dist/`) because the local
distribution folders are not marked as module roots, causing Webpack
to never hit the `module`/`raw-module` resolution hooks and therefore
skipping package exports resolution and breaking secondary entry-points
from being resolved properly (when bundling).

We fix this by also attempting to resolve path mappings as modules,
allowing for Webpacks `resolve-in-package` hooks to be activated. These
hooks support the `exports` field and therefore APF v14 secondary
entry-points which are not necessarily inside a Webpack resolve
`modules:` root (but e.g. in `dist/`)

The E2E test suite contains a production build test (`build/prod-build`) that performs
a size comparison check to ensure a production build of a newly generated application
stays within 10% of a predefined value (currently 124,000 bytes).
As a result of this preexisting check, the need to perform another check that involves
the added complexity of Github status hooks and API calls is currently not needed.

A new E2E test has been added that updates a newly generated application to use a standalone component that
is bootstrapped with the newly introduced `bootstrapApplication` API. This test is intended to check that
the minimal functionality for a standalone-based application functions with the Angular CLI. More expansive
tests will be added as standalone features and capabilities are introduced within the Angular CLI.

It appears that enabling this no longer causes a slugish experience.

…finition file

With the APF changes in version 14, the dts entrypoint file has been changed to `index.d.ts`, this results in TypeScript being able to resolve the type definition file without the need of the additional path to the flat module file dts.

…ibraries secondary entrypoints

`package.json` files have been remove from secondary entrypoints in version 14 of Angular package format (APF).

With this change we delete the now redundant files and in case these contained the deprecated way of how to configure secondary entrypoints in ng-packagr we migrate these as well.

Bumps up the TypeScript version to 4.7.

Expands the version range to allow TypeScript 4.7 and makes the necessary code changes in order to support it.

…elper utility

The http E2E helper utility module is now unused within the E2E tests and can be removed.
This also removes usage of the `request` package which is not an actual dependency of the project.

refactored the code and removed the code smells

…versions utility

This change allows renovate to automatically manage the dependency updates for the `ts-node` package used by the E2E schematic.

The `ɵParsedTranslation` type is now exported from the root entry point and can be used without the `private` deep import.

…se cases

Windows Cmd and Powershell don't support autocompletion, but it can be done with utilities like Windows Subsystem for Linux and Git Bash, which should "just work" due to emulating a Linux environment. This clarifies the error message most users will see to call out the state of the world with regard to autocompletion on Windows platforms.

…operty after use

The `deepCopy` utility function previously set its internal tracking symbol property to `undefined` after completion.
However, this still caused the property to exist with a value of `undefined`. Jasmine 4.1 now checks for symbols with
its `toEqual` expectation which resulted in failing tests. The internal tracking symbol property is now removed instead
via `delete`.

…p to BUILD file

Cleans up all referneces to the old `master` branch.

View Engine application builds are no longer supported and the E2E `--ve` option is a no-op.
This test execution was running a duplicate Ivy application test as a result.