chore: use tsconfig paths for Vite resolution

[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?

Running npm start displayed the following Vite warning:

(!) Your Vite config uses features that are unsupported by `configLoader: 'native'`, which is planned to become the default in a future major version of Vite:
  - `__dirname` (vite.config.ts:77:22). Use `import.meta.dirname` instead     
Set `VITE_CONFIG_NATIVE_IGNORE_WARNING=true` to suppress this warning. 

What changes did you make? (Give an overview)

Enabled Vite’s resolve.tsconfigPaths option and removed the manually configured @ alias.

resolve.tsconfigPaths is no longer experimental as of Vite 8.2.0, so it can be used instead of resolving the alias with __dirname.

Related Issues

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

[netlify]

✅ Deploy Preview for eslint-code-explorer ready!

Name	Link
🔨 Latest commit	8d13274
🔍 Latest deploy log	https://app.netlify.com/projects/eslint-code-explorer/deploys/6a7e5b2d63fd9b0008a327db
😎 Deploy Preview	https://deploy-preview-513--eslint-code-explorer.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
🤖 Make changes	Run an agent on this branch

---

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

[DMartens]

Changes LGTM, thanks.