chore: dont pin eslint-parser, allow eslint 9

[Techn1x]

I think @babel/eslint-parser might have been mistakenly pinned in this PR #41 to an explicit version instead of using ^

This older version 7.23.10 doesn't allow eslint v9, whereas later minor versions like 7.25.1 do

[Techn1x]

No idea why that no-get test is failing 😢

[Techn1x]

I tried a few things to get that no-get test to pass, hoping a dependency had some fixes. No luck there

Decided to make sure the no-get test was passing before my code (even though last main commit was green) - so opened a branch with no diff - turns out that is failing.
#96

So I don't think the updates in this PR are causing the rule failure - something somewhere else has changed.

[NullVoxPopuli]

Thanks for the analysis!

Any chance you'd be able to fix whatever is going on there?

[Techn1x]

Gotta pin down the root cause & try and get that empty PR passing. Given that the failing step clones eslint-plugin-ember project, which passed a month ago (per your last commit on main branch here), I am guessing that eslint-plugin-ember has changed in some way in that month. After cloning eslint-plugin-ember I'll get the step to checkout older commits of that project and see if it works.

Cloning a project for tests isn't very deterministic, wondering if we should pin it to a commit or version anyway. Something to think about after figuring out the issue

[Techn1x]

Some progress over in #97 - I've left some comments there.

[Techn1x]

This PR has the fix to get those tests passing now, needed to import the lockfile. Should be good to go.

[NullVoxPopuli]

Thank you!!