Remove use of freedom-for-uproxy*

[willscott]

freedom-for-uproxy-for-* is detrimental for a couple reasons:

• internal changes to the build process can't be upgraded, so you can't take advantage of our fixes to security bugs like UP-01-003 Worker-based Isolation does not prevent XHR & Sockets etc. #365
• Large amounts of code outside of sandboxes widen the trusted code base, and create more potential for attacks
• Destandardization means that uproxy becomes more tightly tied to specific browsers and increases the work for building implementations for new platforms.

[trevj]

I would like to remove all this too but I would say doing so depends on:
#315

[iislucas]

Steps to do this:

• Write lightweight WebRTC core provider
• Rewrite peer-connection in terms of lightweight provider
• Merge custom logging code and freedom code logger.

Reasons to do this:

• To use new freedom testing infrastructure from freedom we need to be on freedom 0.6
• Freedom 0.6 would need to drop our custom core-provider.

[willscott]

Are you claiming you're not going to have integration tests until after launch? How are you planning to test end-to-end stability?

I'd also add that you don't have a way to do storage in firefox before v0.6, or a way to record freedom.js logs, both of which seem pretty essential.

[iislucas]

We need integration tests for uproxy 0.6; if that means we need freedom 0.6, then we need to do this. I'd like to it done soon as we can after freedom 0.6 is fully functional.

[iislucas]

Now in progress by @trevj and @bemasc

[trevj]

Getting closer! Version 15 of uproxy-lib uses freedom.js 0.6 which eliminates freedom-for-uproxy*. Still working on the other repos...

[willscott]

Should be completed in #638

[dborkan]

Can this be closed now? Or does Firefox work still remain?

[salomegeo]

Done