Remote debugging should be proxied and enabled by default

Background

Starting with Brave v1.2, users can enable the remote debugging option which allows for:

• service calls to be made out to Google (fetching syntax highlighting data, etc)
• Lighthouse audits
• actual remote debugging (connecting to phone, etc)

This setting is in brave://settings/privacy and is DISABLED by default. A more detailed description of this (including the Google network annotation) can be found here: https://github.com/brave/brave-browser/issues/7372#issuecomment-569130105

There is no alert (infobar, etc) when the setting is disabled, so users are left thinking there is a bug

Feature request

1. The calls made out to Google services for remote debugging should be proxied to remove user identifiable information (ex: IP address)
2. The Remote Debugging feature should be defaulted to ENABLED

Steps to Reproduce

1. Fresh profile
2. Visit https://brave.com
3. Open developer tools
4. Go to audit tab
5. Run Lighthouse audit

Actual result:

It fails and there is no UI notifying you ☹️

If you opened via the command line, you WILL see stdout logging which suggests going to brave://settings/privacy and enabling Remote Debugging

Expected result:

It should just work

Reproduces how often:

100%

cc: @jumde @rebron

[0x1eef]

@bsclifton I don’t want to use Remote debugging and I would prefer to keep it off. I was surprised to learn this is enabled by default. Anything that allows remote access to my browser (as I understand this feature) is not okay with me and I don’t want it on nor do I want to use services that rely on it.

[bsclifton]

@francoism90 I think we’re going to remove that setting, as it’s now defaulted to on

You can follow https://github.com/brave/brave-browser/issues/9715 for updates