[Security] Improve handling of address bar display for IPFS and IPNS

[bbondy]

Currently http://test.com.ipns.localhost:8000 shows in the address address bar as ipns://test.com.
However test.com is neither a valid CID nor a DNSLink resolution.

There's also a problem that people that run their own local node, want to retain ipfs:// in their URL bar, but they can't set it as the default gateway.

Currently, we only update the address bar to retain ipfs:// and ipns:// when the user is using the configured Brave node and it is localhost.

We should change this to only keep ipfs:// and ipns:// when the address being loaded when:
i) Using the Brave node and the port matches the Brave node's port.
ii) Using the public node and the port matches the public node, and it is localhost. (Currently we don't do this, so this is new)

This means that something that is not running a gateway that is configured in Brave will not retain ipfs:// anymore like it does with an example local server like http://test.com.ipns.localhost:8000

Test cases:

Test case 1: Non configured localhost should never show as IPFS

1. Create an entry in your hosts file pointing to 127.0.0.1 for test.com.ipns.localhost
2. Load http://test.com.ipns.localhost:8000, it should retain that address

Test case 2: Public gateway

1. Install IPFS Desktop and it should be started on port 8080
2. Load http://127.0.0.1:8080/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS. It should load the content but retain the https://dweb.link/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS URL in the address bar.
3. Set your public gateway to http://127.0.0.1:8080 in settings. And also set Brave to use this public gateway when resolving IPFS URIs.
4. Load https://dweb.link/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS. It should update to an ipfs:// URI.

Test case 3:

1. Set Brave to use the local node
2. Load ipns://brantly.eth
3. It should retain ipns://brantly.eth in the address bar.
4. Load http://brantly.eth.ipns.localhost:48081/
5. It should retain ipns://brantly.eth in the address bar.

[lidel]

Two nits regarding "Test case 2"

• When user enters custom public gateway Brave should always replace raw IP (127.0.0.1) with localhost, as that enables subdomains and origin isolation. Raw IP can't have subdomains and all content roots share the same origin, which we don't want in browser.
• Did you mean:

  - retain the https://dweb.link/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS URL in the address bar
  + retain the https://localhost:8080/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS URL in the address bar

  ?
  (spoofing address of public Origin looks like a bug)

[stephendonner]

Verified FIXED on beta using

Brave	1.22.51 Chromium: 89.0.4389.72 (Official Build) beta (x86_64)
Revision	3f345f156bfd157bd1bea06310e55f3fb2490359-refs/branch-heads/4389@{#1393}
OS	macOS Version 11.2.2 (Build 20D80)

Verified the inline testcases, and filed #14499 about the IPFS URI (localhost vs 127.0.0.1) mismatch.

Test case 1: Non configured localhost should never show as IPFS

1. Create an entry in your hosts file pointing to 127.0.0.1 for test.com.ipns.localhost
2. Load http://test.com.ipns.localhost:8000, it should retain that address

Test case 2: Public gateway

1. Install IPFS Desktop and it should be started on port 8080
2. Load http://127.0.0.1:8080/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS. It should load the content but retain the https://dweb.link/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS URL in the address bar.
3. Set your public gateway to http://127.0.0.1:8080 in settings. And also set Brave to use this public gateway when resolving IPFS URIs.
4. Load https://dweb.link/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS. It should update to an ipfs:// URI.

Test case 3:

1. Set Brave to use the local node
2. Load ipns://brantly.eth
3. It should retain ipns://brantly.eth in the address bar.
4. Load http://brantly.eth.ipns.localhost:48081/ (NOTE: I had to change this to be port 48083 to match)
5. It should retain ipns://brantly.eth in the address bar.

Verification passed on

Brave	1.22.53 Chromium: 89.0.4389.72 (Official Build) beta (64-bit)
Revision	3f345f156bfd157bd1bea06310e55f3fb2490359-refs/branch-heads/4389@{#1393}
OS	Ubuntu 18.04 LTS

Verified test plan from the description #14499 about the IPFS URI (localhost vs 127.0.0.1) mismatch.

Test case 1: Non configured localhost should never show as IPFS

1. Create an entry in your hosts file pointing to 127.0.0.1 for test.com.ipns.localhost
2. Load http://test.com.ipns.localhost:8000, it should retain that address

Test case 2: Public gateway

1. Install IPFS Desktop and it should be started on port 8080
2. Load http://127.0.0.1:8080/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS. It should load the content but retain the https://dweb.link/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS URL in the address bar.
3. Set your public gateway to http://127.0.0.1:8080 in settings. And also set Brave to use this public gateway when resolving IPFS URIs.
4. Load https://dweb.link/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS. It should update to an ipfs:// URI.

Encountered #14499

Test case 3:

1. Set Brave to use the local node
2. Load ipns://brantly.eth
3. It should retain ipns://brantly.eth in the address bar.
4. Load http://brantly.eth.ipns.localhost:48081/ (NOTE: I had to change this to be port 48083 to match)
5. It should retain ipns://brantly.eth in the address bar.

Could not resolve ipns

---

Verification is inprogress

Brave	1.22.56 Chromium: 89.0.4389.72 (Official Build) dev (64-bit)
Revision	3f345f156bfd157bd1bea06310e55f3fb2490359-refs/branch-heads/4389@{#1393}
OS	Windows 10 OS Version 2004 (Build 19041.867)

Test case 1: Non configured localhost should never show as IPFS

1. Create an entry in your hosts file pointing to 127.0.0.1 for test.com.ipns.localhost
2. Load http://test.com.ipns.localhost:8000, it should retain that address

Test case 2: Public gateway

1. Install IPFS Desktop and it should be started on port 8080
2. Load http://127.0.0.1:8080/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS. It should load the content but retain the https://dweb.link/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS URL in the address bar.
3. Set your public gateway to http://127.0.0.1:8080 in settings. And also set Brave to use this public gateway when resolving IPFS URIs.
4. Load https://dweb.link/ipfs/QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS. It should update to an ipfs:// URI.

Note : The source QmV4FVfWRG4hJJKUsS1aU9MK85HYFJtuCmYAj8HetS8qMS is not available hence used http://127.0.0.1:8080/ipfs/bafybeiemxf5abjwjbikoz4mc3a3dla6ual3jsgpdr4cjr3oz3evfyavhwq/wiki/Vincent_van_Gogh.html to test the issue

Test case 3:

1. Set Brave to use the local node
2. Load ipns://brantly.eth
3. It should retain ipns://brantly.eth in the address bar.
4. Load http://brantly.eth.ipns.localhost:48081/ (NOTE: I had to change this to be port 48082 to match)
5. It should retain ipns://brantly.eth in the address bar.

[LaurenWags]

Adding QA/Test-All-Platforms since this issue also has the security label