chore: upgrade vite to v8

[Pixel998]

Prerequisites checklist

• I have read the contributing guidelines.

AI acknowledgment

• I did not use AI to generate this PR.
• (If the above is not checked) I have reviewed the AI-generated content before submitting.

What is the purpose of this pull request?

This PR migrates the project to Vite 8 and updates the React plugin setup to the Vite 8-compatible @vitejs/plugin-react v6 configuration. It also cleans up the related build config changes required by Rolldown/Oxc and fixes the Code Path regression that surfaced during the migration.

In local testing, production builds are about 6x faster and the generated build output is about 5% smaller than with the previous Vite 7 setup.

What changes did you make? (Give an overview)

• Upgraded vite to 8.0.1 and @vitejs/plugin-react to 6.0.1.
• Added @rolldown/plugin-babel and @babel/core, and migrated the React Compiler setup from react({ babel: ... }) to react() plus babel({ presets: [reactCompilerPreset()] }).
• Updated the Vite build config to use Vite 8 / Rolldown-compatible output settings, replacing the old manualChunks setup with codeSplitting.groups.
• Removed old compatibility/configuration bits that were tied to the previous Vite/plugin-react setup, including stale dependency optimizer and chunking config.
• Replaced the use-debounced-effect dependency in the Code Path view with a local debounced effect to avoid the runtime interop error introduced by the tooling migration.

Related Issues

Is there anything you'd like reviewers to focus on?

[netlify]

✅ Deploy Preview for eslint-code-explorer ready!

Name	Link
🔨 Latest commit	3bee6e3
🔍 Latest deploy log	https://app.netlify.com/projects/eslint-code-explorer/deploys/69c2c048ac44260008544a87
😎 Deploy Preview	https://deploy-preview-359--eslint-code-explorer.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[DMartens]

Other than the pre-existing error, changes LGTM.
Would like someone else with more vite experience to double-check.

[amareshsm]

overall it LGTM.

Vite 8 introduces an experimental resolve.tsconfigPaths option that automatically reads path mappings from your tsconfig.json, eliminating the need to manually configure resolve.alias.

resolve: {
  tsconfigPaths: true
}

it’s still marked as experimental so will take it up later.