feat: require-array-sort-compare + toSorted

[Zamiell]

PR Checklist

• Addresses an existing open issue: fixes Bug: [require-array-sort-compare] Does not work with Array.toSorted #8051
• That issue was marked as accepting prs
• Steps in Contributing were taken

Overview

A simple PR that just expands the rule to check for both sort and toSorted (instead of just checking for sort).
For context, when the rule was originally created, toSorted didn't exist, as this is a new array method.

[typescript-eslint]

Thanks for the PR, @Zamiell!

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	51dea59
🔍 Latest deploy log	https://app.netlify.com/sites/typescript-eslint/deploys/65787b379f257b000881fbee
😎 Deploy Preview	https://deploy-preview-8052--typescript-eslint.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 90 (🔴 down 7 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.

[JoshuaKGoldberg]

[Non-Actionable] Aside: I'm glad you didn't increase the complexity of this selector 😂 I think it's at the maximum reasonable level to still be readable as-is...

[Zamiell]

lol, that was because i simply do not know the selector syntax well enough to even try

[JoshuaKGoldberg]

Love it, super straightforward and clean. Thanks! ✨

[JoshuaKGoldberg]

CI failures are unrelated.

[JoshuaKGoldberg]

SHOOT meant to rename the PR to feat(eslint-plugin):. Sigh.

[Josh-Cena]

@Zamiell @JoshuaKGoldberg There's a test failure with this PR because the doc description wasn't updated. One of you want to follow-up?

[Zamiell]

can you direct me to the file (or preferably, the line) that you want me to update?

[Josh-Cena]

This is the error:

Summary of all failing tests
 FAIL  tests/docs.test.ts (195 MB heap size)
  ● Validating rule docs › require-array-sort-compare.md › require-array-sort-compare.md must start with frontmatter description
    expect(received).toMatchObject(expected)
    - Expected  - 1
    + Received  + 1
      Object {
        "depth": 2,
    -   "text": "description: 'Require `Array#sort` and `Array#toSorted` calls to always provide a `compareFunction`.'",
    +   "text": "description: 'Require `Array#sort` calls to always provide a `compareFunction`.'",
        "type": "heading",
      }

So, you would edit the description front matter of require-array-sort-compare.md

[JoshuaKGoldberg]

Zamiell JoshuaKGoldberg There's a test failure with this PR because the doc description wasn't updated. One of you want to follow-up?

Huh, brain fart on my end missing this. Thanks for the catch!