It introduces a preference (network.proxy.allow_bypass) that disables this "feature" (anti-feature for us?) in toolkit/modules/ServiceRequest.jsm.
Please notice that we already disabled it on desktop (#40682 (closed)), but not on Android!
I'd change netwerk/protocol/http/{HttpBaseChannel.cpp,nsHttpChannel.cpp} to ignore the request to use this flag anyway to be on the safe side.
First, I'd make the HTTP channel return NS_ERROR_NOT_IMPLEMENTED from GetBypassProxy/SetBypassProxy like the dummy channel, to avoid future conflicts/compilation errors, in case new parts of the code start using these functions.
On the other hand, having errors at the rebase/first build attempt would be helpful, because it would make us spot immediately such changes.
Then, I'd revert the change in nsHttpChannel.cpp, and set the new network.proxy.allow_bypass to false, to avoid any error due to the not implemented.
efe27c10 introduced also tests on the feature... Should I revert them?