Refactor(data): Implement Store-to-Pipeline Legacy Bridge

Goal

Implement a clean, reactive bridge in Neo.data.Store to automatically transition "simple" stores using the url config to the new Pipeline architecture without breaking existing applications.

Context

Following the removal of the implicit legacy bridge in Store.mjs (#9502), many existing stores that relied on the url config without an explicit pipeline began failing. To maintain a lean App Worker dependency graph while preserving backward compatibility, we need a mechanism that dynamically creates a pipeline only when needed.

Changes

• Reactive Legacy Bridge: Modified beforeSetPipeline in Store.mjs to detect when a url is provided without an explicit pipeline or api. In this case, it triggers a dynamic import of Neo.data.connection.Xhr and generates a "dummy" pipeline configuration.
• Race Condition Prevention: Introduced me.urlPipelinePromise to handle the asynchronous gap between the dynamic import and the initial load() or autoLoad execution.
• Enhanced Load Flow:
  • load() now awaits urlPipelinePromise if it exists.
  • Improved result extraction to correctly handle responseRoot and nested JSON structures.
  • Added safety checks for undefined or null responses from the pipeline to prevent runtime errors.
• Cleanup: Removed the broken Neo.Xhr.promiseJson fallback at the bottom of the load() method, leaving only the Node.js fs/promises fallback for non-browser environments.

Acceptance Criteria

• Stores using only the url config (like Portal.store.Releases) function correctly via a dynamically created pipeline.
• Race conditions during autoLoad are prevented via the urlPipelinePromise.
• Store.load() is more robust and correctly extracts data from diverse pipeline responses.
• The App Worker remains lean by only importing connection.Xhr on-demand.