Webpack: Migrate All Worker Builds to Native ESM Output

Description

Following the successful modernization of the Main Thread build (Ticket #8760), we are extending the Native ESM Output strategy to all Worker builds.

This is a significant architectural shift. By enabling experiments: { outputModule: true } and output.library: { type: 'module' } across the board, we are instructing Webpack to generate true ECMAScript Modules for all worker bundles (App, Data, VDom, etc.).

Benefits:

1. Consistency: Unifies the build output format across the entire framework.
2. Performance: Native ESM can be more efficient for browsers to parse and execute compared to Webpack's legacy wrapper boilerplate.
3. Future-Proofing: Aligns the framework with modern web standards and prepares it for features like Top-Level Await (TLA) in workers.
4. Simplified Chunk Loading: Enables publicPath: 'auto', allowing native import() to resolve chunks relative to the worker file, eliminating the need for manual path patching logic.

Scope

Apply the following changes to all development and production configurations for App Workers and generic Workers:

• buildScripts/webpack/development/webpack.config.appworker.mjs
• buildScripts/webpack/development/webpack.config.worker.mjs
• buildScripts/webpack/production/webpack.config.appworker.mjs
• buildScripts/webpack/production/webpack.config.worker.mjs

Changes Required

1. Add experiments: { outputModule: true }.
2. Set output.library: { type: 'module' }.
3. Set output.publicPath: 'auto' (replacing empty string '').
4. Ensure target remains webworker.

Acceptance Criteria

• All worker bundles (appworker.js, dataworker.js, vdomworker.js, etc.) are generated as valid ES Modules.
• Application boots and functions correctly in both Development and Production builds.
• Dynamic imports inside workers resolve correctly.