As an element developer, I would like to provide multiple mocked configurations and swap between them in the UI

[tueda-hvd]

This would allow a developer to mock up multiple preset configurations for testing and demo purposes. This could work in conjunction with #22 for a more meaningful config/state pairing.

[tueda-hvd]

I was thinking this would take the form of a toolbar or dropdown in the authoring UI that lists out mocked configuration states and loads them on selection. We currently provide an initState to seed a TE configuration on first load; this requested change would allow us to provide multiple configuration states, and allow a user to swap between those via the authoring UI.

I think this configuration would fall under the mocks export alongside displayContext, and entries in displayContext could reference specific mocked configurations, as I could see the interpretation of display state being dependent on the configuration (e.g. if a TE allows the learner to provide multiple inputs, each input may be set with a UUID in the authoring, and the user submission would contain those UUIDs that maps user state to configuration).

Selecting a configuration from the UI would essentially emit the save event with the selection, refreshing both edit and display with the new config.