Make OffTheRecordProfileIOData use its own CTVerifier.

It subclasses ProfileIOData, which always makes and sets a CTVerifier
for the MainURLRequestContext, but the OffTheRecordProfileIOData was
replacing the pointer with on to the system context's CTVerifier. Both
verifiers are created with the same arguments, so this doesn't seem to
server any useful purpose.

The CTVerifier created by ProfileIOData contains no reference to
outside data, other than CTLogs and as an STH Observers, so it should
be fine to use for Incognito mode (Also note that it is not shared
between Incognito and non-Incognito).

BUG=732537

Review-Url: https://codereview.chromium.org/2936643004
Cr-Commit-Position: refs/heads/master@{#478792}

chrome/browser/profiles/off_the_record_profile_io_data.cc

@@ -205,8 +205,6 @@ void OffTheRecordProfileIOData::InitializeInternal(
   ApplyProfileParamsToContext(main_context);
 
   main_context->set_transport_security_state(transport_security_state());
-  main_context->set_cert_transparency_verifier(
-      io_thread_globals->system_request_context->cert_transparency_verifier());
   main_context->set_ct_policy_enforcer(
       io_thread_globals->system_request_context->ct_policy_enforcer());