MapView reuse, integration test suite

[tobrun]

Follow up from #13926 and #13976. Since 7.2.0, our map freezes when used in a View reuse scenario. Since this went unnoticed, I'm am adding a new integration test suite using UiAutomator.

MapView freezes in RecyclerView - 4d98991

• GLSurfaceView, calling OnSurfaceCreated in a similar fashion to OnSurfaceDestroyed.
• TextureView, not destroying the map renderer as part of surface destruction, surface can be recreated

Integration test suite - 676d7dd

This PR introduces an integration test-suite that will harden against regressions. I added a handful of others occurrences that had regressed in the past.

cc @mapbox/maps-android

[tobrun]

@ivovandongen
Both master as before #13926, we do not allow reuse of a MapView using a GLSurfaceView.

Below a gif showing the crash:

The crash occurs when you scroll the MapView back into view. When that happens a nativeOnSurfaceCreated is triggered from the render thread and execution fails on renderer.reset() in map_renderer#L169.

The symbolized stack trace here.

[ivovandongen]

@tobrun Like we discussed on chat. I think ideally we would introduce finer grained callbacks, distinguishing from (EGL) context and surface creation/destroys. Cleanup of the renderer / backend can then happen on the context related signals and no longer on surface signals so that re-use of the context with a different surface can be supported seamlessly.

In the TextureViewRenderer we have plenty of control and it should be relatively easy to do. For the GLSurfaceViewRenderer, I think we can set a custom EGLContextFactory that can provide us the needed signals.

Let's make that a new issue though and continue on this path now.

[ivovandongen]

BTW: great addition of the integration tests! Makes everything so much easier to reproduce.

[LukasPaczos]

Thanks for all those tests! A couple of minor comments/questions below.

[LukasPaczos]