Storybook: Consider how to ensure component args stay in sync with component properties

[daneah]

Component properties are fairly strongly typed, at a minimum aligning to a primitive but in some cases aligning to an enumeration of allowed values of one or more primitive types.

Currently, stories for a component specify a particular set of args that map to some subset of that component's properties, and redefine the type for the arg.

These can and have gotten out of sync, sometimes leading to issues with the display and control of those properties within the stories.

Is there a way we might bring these closer together and ensure they stay in sync long term?