[jumbo] Rename function name to fix a jumbo build fail

call to ConnectToWorkerInterfaceProvider is ambiguous.
because there are same function name.
- workers/dedicated_worker.cc
- workers/experimental/thread_pool.cc
thread_pool.cc was added latest.
so rename to ConnectToWorkerInterfaceProviderForThreadPool.

TBR=japhet@chromium.org

Bug: 746956
Change-Id: I3ad3d51351428c8fc3cbc4b617c41a40b8f7a1b4
Reviewed-on: https://chromium-review.googlesource.com/1198664Reviewed-by: Hwanseung Lee <hs1217.lee@samsung.com>
Commit-Queue: Hwanseung Lee <hs1217.lee@samsung.com>
Cr-Commit-Position: refs/heads/master@{#587924}

third_party/blink/renderer/core/workers/experimental/thread_pool.cc

@@ -242,7 +242,7 @@ void ThreadPoolObjectProxy::ProcessTask(
 }
 
 service_manager::mojom::blink::InterfaceProviderPtrInfo
-ConnectToWorkerInterfaceProvider(
+ConnectToWorkerInterfaceProviderForThreadPool(
     ExecutionContext* execution_context,
     scoped_refptr<const SecurityOrigin> script_origin) {
   // TODO(japhet): Implement a proper factory.
@@ -302,8 +302,8 @@ ThreadPoolMessagingProxy* ThreadPool::GetProxyForTaskType(TaskType task_type) {
             OriginTrialContext::GetTokens(context).get(), devtools_worker_token,
             std::move(settings), kV8CacheOptionsDefault,
             nullptr /* worklet_module_responses_map */,
-            ConnectToWorkerInterfaceProvider(context,
-                                             context->GetSecurityOrigin())));
+            ConnectToWorkerInterfaceProviderForThreadPool(
+                context, context->GetSecurityOrigin())));
   }
   return context_proxies_[proxy_id];
 }