OpenSSL: forward to BoringSSL.

OpenSSL: forward to BoringSSL.

This change will sit in the OpenSSL deps repo. When we switch to BoringSSL,
that patch will update DEPS to point to this revision. This avoids having to
update webrtc and libjingle repos at the same time.

The NaCl build is removed because I believe that all the pointers to it are in
the main Chromium repo and can be switched over. I'd rather get a clear build
error than linking in both OpenSSL and BoringSSL. (Also, forwarding doesn't
appear to work for NaCl targets.)

BUG=393317

[Ryan Sleevi, 2014-07-11 20:52:11]

Sergey knows about the NaCl build and what would need to be updated.

I'd hold off on landing this, lest we need to do any further OpenSSL patches,
until we're ready to flop over.

[agl, 2014-07-11 20:59:37]

On 2014/07/11 20:52:11, Ryan Sleevi wrote:
> Sergey knows about the NaCl build and what would need to be updated.

I can build remoting_client_plugin_nacl successfully in my client, which is the
target that Sergey suggested.

> I'd hold off on landing this, lest we need to do any further OpenSSL patches,
> until we're ready to flop over.

Agreed, although I hope that's next week.