Fix memory leak in renderer destroy

[kiryldz]

PRs must be submitted under the terms of our Contributor License Agreement CLA.
Fixes: < Link to related issues that will be fixed by this pull request, if they exist >

Pull request checklist:

• Briefly describe the changes in this PR.
• Include before/after visuals or gifs if this PR includes visual changes.
• Write tests for all new functionality. If tests were not written, please explain why.
• Add example if relevant.
• Document any changes to public APIs.
• Apply changelog label ('breaking change', 'bug 🪲', 'build', 'docs', 'feature 🍏', 'performance ⚡', 'testing 💯') or use the label 'skip changelog'
• Add an entry inside this element for inclusion in the mapbox-maps-android changelog: <changelog>Fix memory leak in renderer destroy.</changelog>.

Summary of changes

Fix memory leak in renderer destroy.
Previously in surface mode we did not call releasing native renderer as Activity.onDestroy call is happening after Android system was sending SurfaceHolder.Callback.surfaceDestroyed when we have already stopped render thread.

Diagram from the profiler after the fix and several opening / closing activity with MapView

User impact (optional)