Detect chrome remote debug targets over ADB like chrome://inspect

By browsing the [Stetho](https://github.com/facebook/stetho/) source code, it seems like `chrome://inspect` is using Unix sockets to discover remote debug endpoints on the network.

At least Stetho opening a socket on `stetho_PROCESSNAME_devtools_remote`, which seem to be the convention used by `chrome://inspect`, so it should be possible to emulate this behavior by simply probing on sockets with the suffix `_devtools_remote`.

Link: https://github.com/facebook/stetho/blob/master/stetho/src/main/java/com/facebook/stetho/server/LocalSocketHttpServer.java

Start by reading the linked Stetho LocalSocketHttpServer.java file to understand the socket naming convention described in the issue. Then inspect this repository's existing remote-debug-target discovery entry points; the issue does not name a file or test. Done means discovering ADB socket targets with the _devtools_remote suffix, as chrome://inspect does.

Written by the indexing model from the issue text.