[DRAFT] docs: API documentation improvements

[jamesdanielwhitford]

Users API: suggested DX improvements

This PR shows some improvements we have been exploring for the Users API docs.

Problems with the current state

1. The Users API is a single large page containing all operations. The TOC on the right has some structure, but because all operations live on one page the content is extremely long and readers lose context as they scroll.

2. All APIField entries are expanded by default. On parameter-heavy endpoints this means the reader must scroll through hundreds of field descriptions to reach the next operation.

What we changed

The Users API page has been split into 17 sub-pages, one per operation. Each page has a focused TOC with ###-level headings for each request variant, so readers can navigate directly to the lookup method they need. A new CodeExample component renders a minimal copyable curl/Python snippet directly below each endpoint definition.

APIField entries are now collapsed by default using a <details> element. Readers can expand only the fields they care about, significantly reducing scroll depth on parameter-heavy pages.

Next steps

These changes cover the Users API only. If the approach looks good, the same improvements can be rolled out across all other API reference pages.

CI note

The check-apis-against-client-json.rb step in the lint workflow will fail on this PR. It expects to find the built output at dist/docs/apis/users.html, which no longer exists after the page split. Before merging any version of these changes, that script will need to be updated to check the sub-pages at dist/docs/apis/users/*.html instead.