docs(linter): Add doc comments for func_style options.

[connorshea]

This one is a bit weird in that there's an overrides > namedExports option that's nested? But the struct doesn't appear to quite match that expectation. Also, the struct doesn't quite match the fact that there's no key for style, it's just a string value at the top level.

Part of #14743.

Generated docs:

## Configuration

This rule accepts a configuration object with the following properties:

### allowArrowFunctions

type: `boolean`

default: `false`

When true, arrow functions are allowed regardless of the style setting.


### allowTypeAnnotation

type: `boolean`

default: `false`

When true, functions with type annotations are allowed regardless of the style setting.


### style

type: `"expression" | "declaration"`

default: `"expression"`

The style to enforce. Either "expression" (default) or "declaration".

[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 adds documentation comments to the FuncStyle configuration struct fields, improving code documentation for the func_style linter rule. The comments describe each configuration option's purpose and allowed values.

• Added doc comments for all four fields in the FuncStyle struct
• Documentation aligns with ESLint's func-style rule configuration options

---

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

[codspeed-hq]

CodSpeed Performance Report

Merging #14847 will not alter performance

_{Comparing connorshea:func-style-docs (c8580b4) with main (aa024d9)}

Summary

✅ 4 untouched
⏩ 33 skipped¹

Footnotes

1. 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. ↩

[camc314]

thank you!