docs(linter): Add autogen doc support for max_nested_describe in jest plugin. (#14797)

Related to #14743.

This results in the addition of a config block in the docs, like this:

```md
## Configuration

This rule accepts a configuration object with the following properties:

### max

type: `integer`

default: `5`

Maximum allowed depth of nested describe calls.
```

There were also some extra linebreaks I removed from the
`declare_oxc_lint!` call.

Author: connorshea

crates/oxc_linter/src/rules/jest/max_nested_describe.rs

@@ -3,6 +3,7 @@ use oxc_diagnostics::OxcDiagnostic;
 use oxc_macros::declare_oxc_lint;
 use oxc_semantic::ScopeId;
 use oxc_span::Span;
+use schemars::JsonSchema;
 
 use crate::{
     context::LintContext,
@@ -19,8 +20,11 @@ fn exceeded_max_depth(current: usize, max: usize, span: Span) -> OxcDiagnostic {
         .with_label(span)
 }
 
-#[derive(Debug, Clone)]
+#[derive(Debug, Clone, JsonSchema)]
+#[serde(rename_all = "camelCase", default)]
+#[schemars(default)]
 pub struct MaxNestedDescribe {
+    /// Maximum allowed depth of nested describe calls.
     pub max: usize,
 }
 
@@ -39,13 +43,12 @@ declare_oxc_lint!(
     ///
     /// Nesting `describe()` blocks too deeply can make the test suite hard to read and understand.
     ///
-    ///
     /// ### Example
     ///
     /// The following patterns are considered warnings (with the default option of
     /// `{ "max": 5 } `):
     ///
-    /// /// /// Examples of **incorrect** code for this rule:
+    /// Examples of **incorrect** code for this rule:
     /// ```javascript
     /// describe('foo', () => {
     ///     describe('bar', () => {
@@ -118,6 +121,7 @@ declare_oxc_lint!(
     MaxNestedDescribe,
     jest,
     style,
+    config = MaxNestedDescribe
 );
 
 impl Rule for MaxNestedDescribe {