feat(linter): Support auto generate config document for tuple lint option

[xuanduc987]

Related to #15797. This allows configuration for rule like eslint/sort-keys to render correctly.

The generated result is bellow

## Configuration

### The 1st option

type: `"desc" | "asc"`

Sorting order for keys. Accepts "asc" for ascending or "desc" for descending.


### The 2nd option

This option is a object with the following properties:

#### allowLineSeparatedGroups

type: `boolean`

default: `false`

When true, groups of properties separated by a blank line are sorted independently.


#### caseSensitive

type: `boolean`

default: `true`

Whether the sort comparison is case-sensitive (A < a when true).


#### minKeys

type: `integer`

default: `2`

Minimum number of properties required in an object before sorting is enforced.


#### natural

type: `boolean`

default: `false`

Use natural sort order so that, for example, "a2" comes before "a10".

[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.

[codspeed-hq]

CodSpeed Performance Report

Merging #15904 will not alter performance

_{Comparing xuanduc987:push-qrqwopmxyowo (f1450fa) with main (3fe5225)¹}

Summary

✅ 4 untouched
⏩ 41 skipped²

Footnotes

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

2. 41 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. ↩

[connorshea]

I'm glad to see someone working on improving this, thank you 🙏

[connorshea]

A few other rules that will need this in order to get documentation generation working for them (we can do these in later PRs, just making a note):

• func-names
• yoda
• arrow-body-style
• max-dependencies I'm not sure if this one is really fixed by this PR, we may need to add some additional handling, but this PR at least gets us closer to accurately representing it.

[ryansuhartanto]

Another one that I use and notice is import/consistent-type-specifier-style. It accepts a literal string and not an object.

[connorshea]

Tested this locally with the just website command to make sure it came out fine and didn't cause changes on any other pages, and this all looks good to me, thanks!

Only concern is that it doesn't seem to pull the default value for the first option, but we can look into fixing that later.

[connorshea]

Another one that I use and notice is import/consistent-type-specifier-style. It accepts a literal string and not an object.

Thanks! I've added my examples and that one to #16023.