refactor: update imports to use absolute paths for better readability

[lumirlumir]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request?

I'm not sure if I'm the only one who feels this way, but I found that mixing relative and absolute import paths made things a bit messy. So, I've updated the import paths to use absolute paths for better readability and consistency.

I've also alphabetized the import order and arranged them from external dependencies to internal ones, which helps make everything look cleaner.

What changes did you make? (Give an overview)

In this PR, I've updated imports to use absolute paths for better readability

Related Issues

N/A

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

Actually, there are a few more modules where the import paths could be updated, but I intentionally excluded them to keep the scope manageable. For your reference, the ones not included are:

• The ast, path, scope, and ui directories in src/components

[netlify]

✅ Deploy Preview for eslint-code-explorer ready!

Name	Link
🔨 Latest commit	8c3888c
🔍 Latest deploy log	https://app.netlify.com/projects/eslint-code-explorer/deploys/68e8ff196d66430008c0cdd7
😎 Deploy Preview	https://deploy-preview-182--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.

[amareshsm]

LGTM. Thanks.

"I intentionally excluded some directories to keep the scope manageable." - sounds reasonable. If those folders (ast, path, scope, ui) are somewhat self-contained and internal to a larger module (e.g., all part of src/components/), keeping relative imports within them is totally fine. Leaving it open for a while in case others have any additional thoughts or opinions.