Add support for injecting dependencies into Composables

[snappdevelopment]

This adds new functionality to inject classes into Composables, which have the ComposeFragment or ComposeScreen annotation applied.

Before this change users could provide UI specific dependencies via Composes' LocalCompositionProvider. This got removed in favour of injecting directly into the Composable.

Example:
We want to use an instance of MyDependency in the UI, which is provided through Dagger.

@ComposeFragment( //or @ComposeScreen
    scope = Example::class,
    parentScope = Singleton::class,
    stateMachine = ExampleStateMachine::class,
)
@Composable
internal fun ExampleUi(
    myDependency: MyDependency,
    state: ExampleState,
    sendAction: (ExampleAction) -> Unit,
) {

[snappdevelopment]

state and sendAction are specific to our codebase. Not sure how this could be prevented

[gabrielittner]

I think this is fine, for a first step. A better long term solution would be to see how we can get the type parameters of the state machine class and then match based on those. E.g. FooStateMachine which we have extends StateMachine<FooState, FooAction> so we can extract those 2 to use them here.

[gabrielittner]

I think this is fine, for a first step. A better long term solution would be to see how we can get the type parameters of the state machine class and then match based on those. E.g. FooStateMachine which we have extends StateMachine<FooState, FooAction> so we can extract those 2 to use them here.