[Android] Added Happy Eyeballs for address selection

[marcesengel]

Summary

On android IPv6 issues can lead to very long loading times, as first all returned IPv6 addresses for a domain are tried until they timeout and after that IPv4 is used. This PR makes use of the Happy Eyeballs as suggested in #32730.

Changelog

• Added Happy Eyeballs (https://datatracker.ietf.org/doc/html/rfc8305#section-5), missing usage of historical data - fixes Android fetch hangs indefinitely with IPv6 hosts on some devices (Happy Eyeballs) #32730

[Android] [Feature] - Added Happy Eyeballs for network request target address selection

Test Plan

In my local wifi www.google.com was not reachable by IPv6, causing a timeout and failover on the first request. With the proposed PR the IPv4 request was started after the set timeout (t = a + (a * 1.5 ^ 1) + ... + (a * 1.5 ^ (n - 1)) for the nth request, where a = 400 ms) and was elected the winner, cancelling the IPv6 request.

The debug tools only showed one network request.

Edit: Also tried throwing an UnknownHostException in the lookup function, simulated every possible address failing by only calling call.cancel() in onConnectionAcquired and tried the selected address failing by calling call.cancel() at the end of onConnectionAcquired.

[andreialecu]

Note for reviewers:

Reddit deleted their IPv6 AAAA DNS records at one point probably to work around issues with their Android app not implementing Happy Eyeballs:

Ref:
https://www.reddit.com/r/ipv6/comments/r047ah/redditcom_has_deleted_aaaa_records_and_is_back_to/
https://www.reddit.com/r/ipv6/comments/qy70hv/new_phone_failing_to_load_any_ipv6_websites_on/hlebckp/?utm_source=reddit&utm_medium=web2x&context=3

This issue can be quite important.

[cortinico]

See my comment on #33045 (comment) for next steps on how to proceed here.