I happened to have a 2 year old package lock file.
Compare and copy and paste several of the versions and problematic packages.
This could use further review to get the latest but still working versions.
For now, this is good enough to get things compiling.

The `12.2.16` versions of angular happened to be being pulled down by recent installs but the older package lock file shows `12.2.17`.
Explicitly set the `12.2.17` in all angular cases.

Several dependencies have warnings like these:
```
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18.17' },
npm WARN EBADENGINE   current: { node: 'v16.18.1', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18.17' },
npm WARN EBADENGINE   current: { node: 'v16.18.1', npm: '8.19.2' }
npm WARN EBADENGINE }
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package: '[email protected]',
npm WARN EBADENGINE   required: { node: '>=18' },
npm WARN EBADENGINE   current: { node: 'v16.18.1', npm: '8.19.2' }
npm WARN EBADENGINE }
```
Downgrade the dependencies to known versions that do build.

I explicitly set the `typescript` version to `>=4.2.3 <4.4` based on some of the contents of the 2 year old package lock file.
I do not know what is ideal here for the version numbers but this is good enough for now.