feat: add no-unsafe-unary-minus rule

[samestep]

PR Checklist

• Addresses an existing open issue: fixes Rule proposal: no-implicit-coercion using a negative/minus (-) symbol #7076
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

This PR pulls the implementation of the npm package eslint-plugin-unary-minus into this repo, then modifies it to avoid using the TypeChecker methods getUnionType and isTypeAssignableTo which are not public in the TypeScript API; see microsoft/TypeScript#9879.

[typescript-eslint]

Thanks for the PR, @samestep!

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	86b634a
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/653ead7872c36b0008b3cb11
😎 Deploy Preview	https://deploy-preview-7390--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 96 (🔴 down 3 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.

[nx-cloud]

☁️ Nx Cloud Report

CI is running/has finished running commands for commit 86b634a. As they complete they will appear below. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this CI Pipeline Execution

---

✅ Successfully ran 19 targets

• nx test eslint-plugin --coverage=false
• nx test typescript-estree --coverage=false
• nx run types:build
• nx run repo-tools:postinstall-script
• nx test utils --coverage=false
• nx test visitor-keys --coverage=false
• nx test type-utils --coverage=false
• nx test scope-manager --coverage=false
• nx test eslint-plugin-tslint --coverage=false
• nx test rule-schema-to-typescript-types --coverage=false
• nx test repo-tools --coverage=false
• nx run-many --target=typecheck --parallel
• nx test parser --coverage=false
• nx test ast-spec --coverage=false
• nx test eslint-plugin-internal --coverage=false
• nx run-many --target=lint --parallel
• nx run eslint-plugin:generate:configs
• nx run integration-tests:test
• nx run-many --target=build --parallel --exclude=website --exclude=website-eslint

---

Sent with 💌 from NxCloud.

[JoshuaKGoldberg]

A solid start, thanks for sending in! ✨

Requesting changes on using more direct, public APIs, and some more testing.

[JoshuaKGoldberg]

👋 Hey @samestep! Just checking in, is this still something you have time for? No worries if not - I just don't want to leave it hanging.

[samestep]

@JoshuaKGoldberg thanks for the ping! Sorry for dropping the ball on this; I'm taking a look now, will see if I can figure out how to restructure it according to the feedback you gave in August.

[JoshuaKGoldberg]

Looking great! A few comments, mostly more questions than anything else. But I am starting to wonder about increasing the rule's scope... 🤔

[JoshuaKGoldberg]

🚀 swell, thanks!