Summary

Fixes #120125 by normalizing ReactElement signatures in generated API documentation.

ReactElement types were expanding to include verbose second generic parameters like ReactElement<MyProps, string | React.JSXElementConstructor<any>>, making documentation difficult to read. This PR adds a normalizeReactElementSignature helper that strips the redundant second generic while preserving the meaningful first type parameter.

Before / After Example

Given this TypeScript type:

export interface MyProps {
  title: string;
}

export type AReactElementFn = () => ReactElement<MyProps>;

Before this PR:

The generated API docs expanded to verbose, hard-to-read signatures:

{
  "label": "AReactElementFn",
  "signature": [
    "() => React.ReactElement<",
    { "pluginId": "pluginA", "section": "def-public.MyProps", "text": "MyProps" },
    ", string | React.JSXElementConstructor<any>>"  // <-- Verbose noise!
  ]
}

This rendered in the docs as:

() => React.ReactElement<MyProps, string | React.JSXElementConstructor<any>>

After this PR:

The redundant second generic is stripped for cleaner output:

{
  "label": "AReactElementFn",
  "signature": [
    "() => React.ReactElement<",
    { "pluginId": "pluginA", "section": "def-public.MyProps", "text": "MyProps" },
    ">"  // ✅ Clean!
  ]
}

This now renders in the docs as:

() => React.ReactElement<MyProps>

Why This Matters

The second generic parameter of ReactElement (string | React.JSXElementConstructor<any>) is a TypeScript implementation detail that:

• Provides no useful information to API consumers
• Clutters the documentation with boilerplate
• Makes signatures harder to scan and understand

Changes

• Add normalizeReactElementSignature() in get_signature.ts to clean up ReactElement output before reference extraction
• Re-enable the previously skipped Test ReactElement signature test
• Update integration test snapshots to reflect the normalized signatures