…g-to-17

…into issue-upgrade-primeng-to-17

Update nx version to the latest and make it consistent. This should
resolve issues causing #29415 (Flakey build. coreweb yarn install Bus
Error core ).

See https://nx.dev/nx-api/angular/documents/angular-nx-version-matrix

https://nx.dev/nx-api/workspace/documents/nx-nodejs-typescript-version-matrix
https://v17.angular.io/guide/versions

https://nx.dev/changelog

The main issue seems to be related to @nx/linter19.5.1 being added and
it not matching the rest of the nx modules with 18.3.5. Also separately
@nxext/stencil did not have a matching version to nx at 17.2.2. 17.x
versions of @nxext/stencil pull in other nx dependencies and needs an
exact version match, nx 18.x.x needs @nxext/[email protected] and nx 19.x.x
needs @nxext/[email protected]

The conflicting versions showed up with "yarn list", nx versions can be
upgraded with the "nx migrate" command.

I have upgraded to the latest nx here after reviewing documents and any
breaking changes, but if there are problems preventing the nx update we
can try changing the nx version back to 18.3.5 and use a matching
version of @nx/linter as well as @nxext/[email protected] to match

Putting it in a centralized place.
Adjusting a couple of tests to reflect this logic change.
Also since from the provided logs there was an Jackson parsing error,
new fields were added to "DTO" class to consider the error field.
Initially when implementing IT for AI classes, I took the approach of
mocking or building an `AppConfig` class on the flight instead of
creating an `dotAI` app secrets so config classes can be created out of
them. Just as it happens at production code. I'm introducing some
changes to correct this as well.

…into issue-upgrade-primeng-to-17

…into issue-upgrade-primeng-to-17