fix: set espree range: true to fix scope crash

[xbinaryx]

Prerequisites checklist

• I have read the contributing guidelines.

What is the purpose of this pull request?

Fix a crash in the scope analyzer caused by missing node.range on nodes when parsing JavaScript.

The scope analyzer relies on node.range to be present. In particular, FunctionScope.__isValidResolution reads this.block.body.range[0] and d.name.range[0]. Espree’s default is range: false, so without enabling it, node.range is undefined, and accessing [0] throws Cannot read properties of undefined (reading '0').

Note: As a side effect of enabling range: true, the AST Tree view now displays a range property on each node.

What changes did you make? (Give an overview)

Set range: true in espree.parse so nodes include the range property required by the scope analyzer.

Related Issues

Fixes #125

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

[netlify]

✅ Deploy Preview for eslint-code-explorer ready!

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

Verified it is working as expected - Preview Link