[Feature] Add a declarative api

[Nek-12]

[Feature] Add a declarative api

[maxkeppeler]

UseCastState could continue to exist as an internal abstract remembered state, and the parameter visible could be extracted from it. This would replace useCaseState with visible for dialogs, views, etc. However, I don't see this change being worth the effort and time.

[Nek-12]

I understand the decision. We are not against creating declarative wrappers for our dialogs, however the parameter visible in the dialog is remembered and not used as a key, which means it will not react to property change, forcing us to use the LaunchedEffect of sorts to manage it. Would it be possible to add the visible parameter as a key to the useCaseState then to make it react to changes ?