Update based on BoringSSL relicense?

[joshtriplett]

As of 2 weeks ago, upstream BoringSSL did all the legwork to relicense to Apache 2.0, eliminating the OpenSSL license: google/boringssl@33d1049

This in theory would make it much easier for aws-lc to follow suit, which makes it easier for applications to choose a library to use.

(ring seems to be following suit soon, and I'd like to avoid the scenario where people need to choose between ring vs aws-lc based on licensing rather than based on other factors.)

[skmcgrail]

@joshtriplett We are exploring and evaluating what, if any, options we could take to potentially relicense the project. At this time though we don't have a specific date or timeline we can share on when such a determination will be made.