fix(export,scope): record the Java types a model names as dependencies

[joaodinissf]

Fixes #1554

Why the change

A change to a Java class that an export or scope model names only by name (an extension, an inject, or a type in an expression) now re-queues the model, so its generated Java no longer goes stale.

Special things to note

• These names are only resolved while the Java is generated, so before this change they were neither references nor imported names of the model. Types that the generated model references directly were already tracked, through its references.
• Only names the model states are added; the inferred JVM model's own imported names are left as they are. Recording those as dot-separated names (they are currently single-segment and never match) is a separate change.
• An include cycle between scope models still overflows the stack in the Scope inferrer; that is pre-existing and not changed here.

Change outline

Where the pieces live:

 com.avaloq.tools.ddk.xtext.expression/
+└── resource/AbstractExpressionModelResourceDescriptionManager.java   # adds the named Java types to the imported names
 com.avaloq.tools.ddk.xtext.export/
+├── resource/ExportResourceDescriptionManager.java                    # extension classes, expression types
 └── ExportRuntimeModule.java                                          # + binding
 com.avaloq.tools.ddk.xtext.scope/
+├── resource/ScopeResourceDescriptionManager.java                     # + inject types, and those of included models
 └── ScopeRuntimeModule.java                                           # + binding

What a model imports now:

 imported names of a model
   names from linking and from the inferred JVM model     (unchanged)
+  extension classes                   com::acme::^export::Util  -> com.acme.export.util
+  inject types (Scope)                com.acme.util.Helper      -> com.acme.util.helper
+  qualified types in expressions      (com::acme::Node) this    -> com.acme.node
+  the same for every included scope model (cycle-guarded)

Tests, red-green checked (bindings removed: these fail; restored: 380 tests, 0 failures):

• ExportResourceDescriptionManagerTest: extension class and expression types are imported and affect the model.
• ScopeResourceDescriptionManagerTest: own and included extension, inject and factory types are imported, and a type only an included model names affects the model; a model without them is not affected.

🤖 Generated with Claude Code

[rubenporras]

since this is a protected method and all consumers use split to create an array, why not have the input parameter String[]? You can have a stream on the array as well and avoid the object creation.