Make Android test enviorment can run browser tests with mojom bound to frames.

[sangwoo108]

[ERROR:render_process_host_impl.cc(5236)] Terminating render process for bad Mojo message: Received bad user message: No binder found for interface cosmetic_filters.mojom.CosmeticFiltersResources for the frame/document scope
I  326.832s run_tests_on_device(192.168.0.13:5555)  [ERROR:bad_message.cc(29)] Terminating renderer for bad IPC message, reason 123

content::SetBrowserClientForTesting() didn't work for Android. We might have to override TestContentBrowserClient.

[arthuredelstein]

Here's an approach I took to fix this problem for one test: brave/brave-core@67293eb. The key was to use BraveContentBrowserClient because it registers a binder for CosmeticFiltersResources. Perhaps this approach can inspire a general solution?

[sangwoo108]

Hum, I thought It hadn't worked at the time. Let me check out again.

[bridiver]

@arthuredelstein @sangwoo108 yes, the problem is that cosmetic filters applies to every frame so no matter what you navigate to, it will try to register the browser interface and fail. Setting the test content browser client to BraveContentBrowserClient is the fix, but what we may want to do is create BravePlatformBrowserTest that is BraveAndroidBrowserTest on android and BraveInProcessBrowserTest on desktop and automatically sets the content browser client to BraveContentBrowserClient

[bridiver]

looks like there are some other issues here as well which I'm investigating

[bridiver]

https://github.com/brave/brave-core/pull/20825/files#diff-12d073f3a7b2147b2fcffec0a1531beec283db0aa6236495f8397d5f68743664

[bridiver]

just looking at some of the upstream browser tests that are now failing to make sure they all should be failing or move them to a follow-up