fix(utils): improve error message on typed rule with invalid parser

[JoshuaKGoldberg]

PR Checklist

• Addresses an existing open issue: fixes Feature: getParserServices should throw informative error when used with non-typescript-eslint parser #6814
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

Adds a small regex in getParserServices to catch common cases of incorrect parsers. It's not comprehensive (../parser.js unfortunately passes) but it does catch the common case of node_modules/@babel/*.

Note that this only augments the existing error message. It doesn't add any new error catching / situations where getParserServices would throw.

[typescript-eslint]

Thanks for the PR, @JoshuaKGoldberg!

typescript-eslint is a 100% community driven project, and we are incredibly grateful that you are contributing to that community.

The core maintainers work on this in their personal time, so please understand that it may not be possible for them to review your work immediately.

Thanks again!

---

🙏 Please, if you or your company is finding typescript-eslint valuable, help us sustain the project by sponsoring it transparently on https://opencollective.com/typescript-eslint.

[netlify]

✅ Deploy Preview for typescript-eslint ready!

Name	Link
🔨 Latest commit	649917f
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/6599fbb18071ba0008542e55
😎 Deploy Preview	https://deploy-preview-8146--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 99 (no change from production) Accessibility: 100 (no change from production) Best Practices: 92 (no change from production) SEO: 98 (no change from production) PWA: 80 (no change from production) View the detailed breakdown and full score reports

---

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

[bradzacher]

Note: probably class this as a fix for semver purposes