typechecking on client generator

[Tcharl]

Second try for #27097
contribute to #26114

Please make sure the below checklist is followed for Pull Requests.

• All continuous integration tests are green
• Tests are added where necessary
• The JDL part is updated if necessary
• jhipster-online is updated if necessary
• Documentation is added/updated where necessary
• Coding Rules & Commit Guidelines as per our CONTRIBUTING.md document are followed

When you are still working on the PR, consider converting it to Draft (below reviewers) and adding skip-ci label, you can still see CI build result at your branch.

[Tcharl]

Please give more comment or accept: I'm not pushing complete change at once by fear of conflicts or monster reviews. Every pr contributes to an objective and is incremental

[mshima]

@Tcharl see #27152, this is caused by circular dependency.
So JDL should be completely independent.
For example we should use generic:

Entity A
search A with current (or any)

instead of:

Entity A
search A with elasticsearch (or couchbase)

[Tcharl]

So let's fix that glitch.
Leaf gen should point to a base gen (look to be the case, respect!), specific jdl dsl should point to an aggregator (convert/export).
State machine is the core (generator tasks) iterates over contributions (generators implementation). Jdl is like a cli, thus at the early steps of the lifecycle.
To me

• Definition is at the root (object), can be modularized
• command and jdl feed the instances
• generator templates consumes instances.

There shouldn't be any technological circular dependency but the ones between generators if they are not well designed

[mshima]

@Tcharl with #27203 configs added to command.configs will automatically appear on jhipsterConfig and jhipsterConfigWithDefaults.