The default cache size is 1,000, which is effectively unbounded
for mobile apps, which likely call a few dozen API servers, ad
networks, and analytics systems.
I don't expect DnsOverHttps to be deployed in other environments.
If so, it's possible this cache will be problematic, as even
10-second stale results can be problematic for server
environments. I'll put an appropriate warning about this in our
release notes.
* Rename includeHttps to includeServiceMetadata
'HTTPS' is way too confusing for DnsOverHttps, because it's about
a DNS record type and not the transport for which records are
retrieved.
* Fix another includeHttps use
* New tests for HTTPS records
* Honor resolvePrivateAddresses and resolvePublicAddresses in DnsOverHttps
* Spotless
* Test canceling after a partial success
* Use a volatile to track whether it's canceled
* Spotless
