Issues with `use-statechart` api

[yenda]

Currently use-statechart can only start the statechart colocated in the component where it is used, under the :statechart key.

The ui-routes namespace on the otherhand uses the statechart under the ro/statechart key.

I'd suggest using a consistant key for both, but I'm also wondering about the current use-statechart implementation, here are my suggestions:

• it should not provide config and local-state because those feel like anti-patterns in the use of statecharts, instead if a user wants the statechart to have an effect on the UI it should be through the :actor/component that is automatically set, and the props can then be added to the component's query as commonly done with ui/props in fulcro
• config and local-state may still be returned via a debug? option
• statechart should be an option (which would eliminate the need to lookup :statechart option of the component and allow multiple different statecharts to be used)

[awkay]

Of these, I think that eliminating the :statechart co-location option completely, and requiring it as a parameter is the primary change I'd make. Just because I happen to think you should use it in a particular way doesn't mean that I should force you to, and many people will just want to leverage the config/state of the chart as input to their UI and completely ignore the aliases and actors.