Investigate the feasibility of newer Mozilla Android components for sessions

[HollowMan6]

Configuration

Wolvic version: main (gecko)
Wolvic build ID: main

Hardware: Any

Related issues

• CORS errors on same origin inconsistent with other browsers (Same Origin Policy) #1097
• Download dialog cannot show repeatedly #353
• Media stream detached from window in some cases? #598
• Saving and loading don't work in Brushworkvr app #87
• Rendering artifacts in Atomic City scene of Mozilla Hubs #86 (Probably related to this as well)

Current Behavior

Chromium doesn't have these similar issues, and those are mostly not reproducible in Firefox for Android

Expected Behavior

All those issues should be resolved.

Possible Solution

Nothing weird can be spotted when debugging our codebase. So those can be caused because we handle the gecko session differently than Fenix (Firefox for Android). We started to notice the difference between Wolvic and Fenix when working on the find-in-page feature #929 (comment), as Fenix heavily depends on browserStore and EngineView, while we use the lower level API to interact with the session. It can be that, by the time FxR was born the only available API was the GeckoView interface. Then Mozilla built some other components on top.

So later, if we find those new Mozilla Android components still compatible to integrate with another backend (i.e Chromium), we can consider refactoring our codebase and moving everything there. This can be a root fix as I guess Gecko may not expect people to use these lower-level APIs now, so they can be very buggy (e.g. caches didn't get cleared correctly when reloading / all media sessions' sound gets muted when we close a tab) if we continue using them.

Context

#1100

Error Logs and Stack Traces