Enhance Data Worker to Instantiate Dynamically Loaded Modules

Goal

Enhance the Data Worker's remote method access to not only import() ES modules but also instantiate them using a provided configuration object, and wire this up to Neo.data.Store.

Context

To keep the App Worker lightweight, it should not import Parser or Normalizer classes. Instead, the Store config will define a config object (e.g., { module: 'Neo.data.normalizer.Tree', childrenProperty: 'items' }). When the Data Worker receives this config, it must load the module and immediately create an instance to be used by the connection pipeline.

Acceptance Criteria

• Create a new createInstance({config}) remote method in Neo.worker.Data.
• The method must import() the required module based on the class name or path, and then use Neo.create(module, config) to instantiate it.
• Store the resulting instance in the Data Worker (e.g., inside an instances map keyed by ID) and return the instance ID to the App Worker.
• Implement afterSetNormalizer(value, oldValue) in Neo.data.Store. If the value is a config object, it must call the Data Worker's createInstance via RMA to ensure the normalizer is ready before data loading begins.
• Document that Parsers and Normalizers must be classes, not singletons, to ensure thread safety.