Add API docs to Storybook

[fredvisser]

😯 Problem to Solve

We would like to display great API documentation and maintain it in a low-effort way. This includes the entire API of a component, for example:

• element name
• property and attribute names (and how they map to each other if it's not obvious; see Storybook property name inconsistencies #824 ), types, and meaning
• event names, event data types, and their meaning
• method names, types of inputs and outputs, and their purpose
• slots
• accessibility concerns
• first class support for all of the above in each of our frameworks, where member names often differ in capitalization or other ways

💁 Proposed Solution

Currently we maintain some of this manually in Storybook, but a lot of it is missing and there may be better ways to autogenerate it from source. Storybook supports several tools to extract this information from the component definition and pull it into Storybook.

1. We're currently using @storybook/html which doesn't support autogenerated API documentation, but it should be trivial to switch to @storybook/web-components which does.
2. @storybook/web-components uses the custom-elements-manifest tool to extract API documentation from the component. It has support for FAST element, but doesn't yet have support for components defined on FAST foundation.

[msmithNI]

Duing the Innovation Day on 6/14/2023 I did some prototyping with TypeDoc for generating API docs from our TypeScript comments on nimble-components:
Storybook
branch

[m-akinc]

It's not clear to me what this is blocked on, so I'm removing the label.

[jattasNI]

I didn't realize this issue existed. I've been using #824 to track this work. The basics are done now and there's already a list of remaining items in that issue, so I'm going to close this one.