docs(linter): Expose use-isnan rule config options.

[connorshea]

So it'll now get picked up by the auto-generated documentation. Part of #14743.

Generated docs:

## Configuration

This rule accepts a configuration object with the following properties:

### enforceForIndexOf

type: `boolean`

default: `false`

Whether to disallow NaN as arguments of `indexOf` and `lastIndexOf`


### enforceForSwitchCase

type: `boolean`

default: `true`

Whether to disallow NaN in switch cases and discriminants

[graphite-app]

How to use the Graphite Merge Queue

Add either label to this PR to merge it via the merge queue:

• 0-merge - adds this PR to the back of the merge queue
• hotfix - for urgent hot fixes, skip the queue and merge this PR next

You must have a Graphite account in order to use the merge queue. Sign up using this link.

An organization admin has enabled the Graphite Merge Queue in this repository.

Please do not merge from GitHub as this will restart CI on PRs being processed by the merge queue.

[Copilot]

Pull Request Overview

This PR exposes configuration options for the use-isnan linter rule by adding JsonSchema derivation and serde annotations, enabling auto-generated documentation for the rule's enforceForSwitchCase and enforceForIndexOf configuration options.

Key Changes:

• Added JsonSchema derive macro to the UseIsnan struct
• Added serde rename_all annotation for camelCase config keys
• Registered the config struct with the linter macro

---

_{Tip: Customize your code reviews with copilot-instructions.md. Create the file or learn how to get started.}

[codspeed-hq]

CodSpeed Performance Report

Merging #14844 will not alter performance

_{Comparing connorshea:use-isnan-docs (720ea6e) with main (d0faa7c)¹}

Summary

✅ 4 untouched
⏩ 33 skipped²

Footnotes

1. No successful run was found on main (302c20c) during the generation of this report, so d0faa7c was used instead as the comparison base. There might be some changes unrelated to this pull request in this report. ↩

2. 33 benchmarks were skipped, so the baseline results were used instead. If they were deleted from the codebase, click here and archive them to remove them from the performance reports. ↩