Fix DNS timing issue caused by UseDnsHttpsSvcbAlpn feature

Chrome starts H1/2 connection job (MAIN job) only after H3 connection
job (DNS_ALPN_H3 job) checks the HTTPS DNS record. This is causing DNS
lookup time to be very small if Chrome can't use the H3 connection.

To solve this issue, this CL plumbs the `dns_resolution_start_time_`
and `dns_resolution_end_time_` from the QuicSessionPool::DirectJob to
the HttpStreamRequest.
  QuicSessionPool::DirectJob::OnResolveHostComplete()
    HttpStreamFactory::Job::OnQuicHostResolution()
      HttpStreamFactory::JobController::OnQuicHostResolution()
        HttpStreamRequest::SetDnsResolutionTimeOverrides().
And HttpNetworkTransaction::OnStreamReady() get the timing information
from HttpStreamRequest, and set them in
HttpNetworkTransaction::GetLoadTimingInfo().

Bug: 41488125
Change-Id: I5461a315fa6693c2f0a6cedd046b07f7adc4782a
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5619831
Reviewed-by: Kenichi Ishibashi <bashi@chromium.org>
Commit-Queue: Tsuyoshi Horo <horo@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1315043}