Create recipe(s) for interop with native iOS

[JessalynWang]

Provide recipes that demonstrate App Platform interop with iOS. For example: similar to how we have native Android support for Views, it is possible to connect presenters with SwiftUI so business logic can be shared in multiplatform while UI remains native.

Candidate topics for these recipes are:

• How to connect presenters to SwiftUI
• How to handle navigation with a presenter backstack and SwiftUI's NavigationStack
• How scopes can be managed from native iOS

As part of these recipes we'll also likely want to demonstrate some sort of pattern for DI. Maybe DI is also a recipe of it's own? Organization of topics into recipes and the scope of what we should cover is still unclear.

[JessalynWang]

I started in a branch, and realize that there are a couple different methods of integration that we should probably address. One is easily covered by what we do internally and the original intention of this issue, but the other two are a bit more abstract.

1. Launching and rendering views for presenters from SwiftUI and with SwiftUI Views. This is what we do internally, and we should be able to expose our internal APIs along with an example of DI to demonstrate how to do this
2. Launching and rendering presenters from Compose to SwiftUI. This is ideally what we would do with the Recipes app, since our other recipes use CMP for UI and should stay like that, while the recipe for SwiftUI should demonstrate a presenter that results in some SwiftUI being shown. Currently RendererFactory gets in the way, and we need to think about how we want to support the inter-op, if at all. (Branch)
3. Embedding SwiftUI in ComposeRenderer. This one is more ambiguous and it is unknown if we can support at this time, needs experimentation. If we can we will introduce SwiftUiRenderer

[JessalynWang]

After thinking about it a bit more, I'm going to kick these:

Launching and rendering presenters from Compose to SwiftUI. This is ideally what we would do with the Recipes app, since our other recipes use CMP for UI and should stay like that, while the recipe for SwiftUI should demonstrate a presenter that results in some SwiftUI being shown. Currently RendererFactory gets in the way, and we need to think about how we want to support the inter-op, if at all. (#156)

Embedding SwiftUI in ComposeRenderer. This one is more ambiguous and it is unknown if we can support at this time, needs experimentation. If we can we will introduce SwiftUiRenderer

to their own issue. It requires more experimentation and is not related to the original scope of this one. Additionally, the outcome of this investigation may be APIs rather than recipes, or we may decide to do nothing at all.

See #158