docs(linter): Add configuration option docs for promise/no-callback-in-promise rule.

[connorshea]

Part of #14743.

Generated docs:

## Configuration

This rule accepts a configuration object with the following properties:

### callbacks

type: `string[]`

default: `["callback", "cb", "done", "next"]`

List of callback function names to check for within Promise `then` and `catch` methods.


### exceptions

type: `string[]`

default: `[]`

List of callback function names to allow within Promise `then` and `catch` methods.

[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 refactors the no_callback_in_promise rule to rename the callbacks configuration field to exceptions and adds schema support for better configuration handling.

• Renamed the configuration field from callbacks to exceptions with clearer documentation
• Added JsonSchema derive and serde attributes for proper schema generation
• Updated all references to use the new exceptions field name

---

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

[connorshea]

Actually I think Copilot is right and I misunderstood the intent of the callbacks config field here, it's distinct from exceptions (which was not previously represented in the config struct, and callbacks never existed in the original ESLint rule, which is the source of my assumption/confusion).

[codspeed-hq]

CodSpeed Performance Report

Merging #15176 will not alter performance

_{Comparing connorshea:no-callback-in-promise-docs (a0ecc57) with main (1b9f6fc)¹}

Summary

✅ 4 untouched
⏩ 33 skipped²

Footnotes

1. No successful run was found on main (baaeca8) during the generation of this report, so 1b9f6fc 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. ↩