fix: standardize webpack 5 dev server, fix MUI exports, and migrate to ESLint v10 flat config to restore npm run dev

[YASHMAHAKAL]

Description

Summary
This PR restores npm run dev to a clean, stable, and fast working state. It resolves breaking CLI crashes caused by deprecated Webpack 4 APIs, fixes over 300+ Material UI export warnings, and decouples ESLint from the HMR pipeline to comply with ESLint v10 standards. Zero source-code (src or HTML) files were modified.

Changes

• Webpack 5 Optimization:
  • Removed deprecated Webpack 4 plugins (NamedModulesPlugin, HotModuleReplacementPlugin) and CLI properties (disableHostCheck, inline).
  • Added devServer.static to restore legacy root-directory serving, natively resolving the Cannot GET / HTML rendering error.
• Fixed MUI v7 Module Coercion:
  • Removed the babel-loader rule that forced @mui|@emotion ESM exports into CommonJS formats. This restores native ESM static analysis and eliminates the 314+ "module has no exports" warnings.
• ESLint v10 Architecture:
  • Converted deprecated .eslintrc config to the mandatory eslint.config.js Flat Config format using the built-in espree JSX parser.
  • Decoupled eslint-webpack-plugin from Webpack. This prevents hard crashes in the dev server (scopeManager.addGlobals is not a function) and completely protects the build pipeline from downstream Node v18 + ESLint v10 CLI formatting conflicts.

Signed commits

• Yes, I signed my commits.

[YASHMAHAKAL]

@Rajesh-Nagarajan-11, @saurabhraghuvanshii take a look please

[leecalcote]

Are we able to deeplink to a specific row in the table? It will have an example if we can. Or alternatively, if we’re able to link to the table with a predefined filter on which rows it displays, that will work, too..

[leecalcote]

If we don’t have them now, a new issue could be opened to create some tests. If we do have some tests, an issue can be open to ensure that they run on open of a pull request.