Browser: Fix Request Error page

[cookiengineer]

The stealth:fix-request error page needs integration to download cached URLs from connected Peers - and in case no Peer is available - the Web Archive.

• [ ] Integrate download from the URL scheme https://web.archive.org/<original url> which will redirect the request to the latest known and scraped archive entry.
• [ ] Integrate button with the UI flow.
• [ ] Integrate local peers and query their cache for the current URL. If available, offer to download from Peer's cache(s) with information about their latest timestamp.

[cookiengineer]

In order to ease up UX, when a Website was successfully downloaded via Peers, the BROWSER.back() method should be called, so that the correct URL is being rendered in the Webview.

• [ ] Add BROWSER.back() call on successful downloads via Peers.
• [ ] Add BROWSER.navigate('https://web.archive.org/' + url); call when an entry was found in the Web Archive.

[cookiengineer]

The fix-request error page now has to be renamed to fix-connection, as the Connection refactor led to multiple error scenarios that all transport protocols now may trigger.

The list off error events as of now are these:

• [x] { type: 'connection' }
• [x] { type: 'connection', cause: 'socket-trust' }
• [x] { type: 'connection', cause: 'socket-stability' }
• [x] { type: 'connection', cause: 'socket-proxy' }
• [x] { type: 'connection', cause: 'headers' }
• [x] { type: 'connection', cause: 'payload' }
• [x] { type: 'host' }

[cookiengineer]

The new Browser Page was successfully renamed and has been integrated as browser/internal/fix-connection.html.

Still missing is the Web Archive Integration, which is temporarily on hold until the Multicast Peering Refactor has been implemented.