IssueTracker

Please remove usages of `getHostView` in pointer input benchmark tests:

```
compose/ui/ui/benchmark/src/androidTest/java/androidx/compose/ui/benchmark/input/pointer/ComposePreciseFingerTapIntegrationBenchmark.kt
compose/ui/ui/benchmark/src/androidTest/java/androidx/compose/ui/benchmark/input/pointer/ComposePreciseStylusTapIntegrationBenchmark.kt
compose/ui/ui/benchmark/src/androidTest/java/androidx/compose/ui/benchmark/input/pointer/ComposeTapIntegrationBenchmark.kt
```

These three benchmarks are preventing us from removing `getHostView()`.  Benchmarks should generally be written in such a way that they can be tested on multiple platforms (using only common-code) to ensure Compose performance good across platforms.  For example, if we care about touch events or STYLUS performance on Android, we probably care about it on iOS too.  To achieve this, rather than directly creating a `android.view.MotionEvent` event within the test and passing it directly to an `android.view.View`, the test should interact through some platform-independent wrapper (which should probably live in the test-utils module).

I'm not super familiar with the structure of test-utils, so take this with a grain of salt, but at first glance, I might consider adding a `dispatchMotionEvent()` function to `ComposeExecutionControl` class, where the dispatchMotionEvent function does not take a `android.view.MotionEvent` but instead takes parameters like this: https://github.com/JetBrains/compose-multiplatform-core/blob/jb-main/compose/ui/ui/src/skikoMain/kotlin/androidx/compose/ui/ImageComposeScene.skikoMain.kt#L232 - I'm not positive if `ComposeExecutionControl` is the right place for this, would defer to whomever owns that module.