Explore support for secondary platforms (car, watch, tv, etc)

[sargunv]

It would be nice to enable building map apps for Android Auto / Android Wear / Google TV / watchOS / tvOS / CarPlay.

Some open questions:

• Is Compose supported at all on any of these platforms? If no, that'd be a blocker.
• Does MapLibre for Android/iOS work on these platforms? If no, that'd be a blocker.
• If yes and yes, do we need to do anything special? If no, then at least the demo app should have examples on how to do it.
• If we need to do something special, what needs to be done? At a minimum, the additional Apple platforms have their own build targets, and I believe the car platforms tightly restrict how you develop UI

[sargunv]

Is Compose supported at all on any of these platforms? If no, that'd be a blocker.

Compose Runtime: yes everywhere

Compose Foundation / UI:

• WearOS: yes
• Android for Cars: I think no
• Android TV: yes
• watchOS: no
• tvOS: no
• CarPlay: I think no

extra: possible research material for cars: https://www.youtube.com/watch?v=6UULcs0cA7g

may be viable to eventually provide non-compose multiplatform helpers for non-compose platfoms to still share code (if MapLibre Native works in more places than Compose does). Would require our architecture to decouple the SDK wrappers and custom compositions (layers, annotations, etc) from Compose UI/Foundation, and have a Compose UI component plug in to that wrapper the same way a non-compose component would

[sargunv]

Android Auto requires rendering the map to a Surface: https://developer.android.com/training/cars/apps#declare-surface-permission

The Android MapLibre SDK couples rendering to a view, but my plan for #218 is to render to a surface provided by Compose. So this code would probably be useful for Auto, once things are decoupled from Compose UI.