ESC docs: drive provider/rotator schema-reference tables from a data source

[jkodroff]

Follow-up from #19691 (and related to #19690).

Problem

The schema-reference tables on ESC provider and rotator pages (Inputs / State / Outputs and their nested type tables) are hand-authored Markdown today. This makes them:

• Inconsistent in column headers and ordering across pages.
• Easy to drift out of sync with the actual provider/rotator schemas.
• Tedious to maintain when a schema changes.

During #19691 the rotator tables were normalized by hand, but the underlying maintainability problem remains.

Proposal

Introduce a data-driven schema-reference structure for ESC provider/rotator pages:

• Store provider/rotator schemas in a data/ source (single source of truth).
• Render the Inputs/State/Outputs tables via a Hugo shortcode that consumes that data.
• Derive the schema from the Pulumi Cloud REST API docs (the rotator/provider schemas are described there).

This mirrors how other generated reference content works on the site and removes the hand-maintained tables.

Notes

• Scope/design details to be fleshed out.
• Ties into ESC: Revise providers pages #19690's goal of improving provider-page scannability/consistency.

🤖 Generated with Claude Code