Move TranslateHelper to the translate component.

components/translate/content/renderer/DEPS

Index: components/translate/content/renderer/DEPS
diff --git a/components/translate/content/renderer/DEPS b/components/translate/content/renderer/DEPS
index 826b97f5af852792056f77f54414d40d25539bc9..a0023b4785725974b5646bd2af9ed2dcdadc5609 100644
--- a/components/translate/content/renderer/DEPS
+++ b/components/translate/content/renderer/DEPS
@@ -1,4 +1,6 @@
 include_rules = [
   "+content/public/renderer",
   "+third_party/cld_2",
+  "+third_party/WebKit/public/web",
+  "+v8",

[Takashi Toyoshima, 2014/09/16 06:51:55]

Is there any reason of that adding WebKit and v8 is ok, but adding extensions is
bad here?
I guess we do not want to have a dependency to a module that does not exit on
mobile platforms, and extensions is the case. But, I do not think WebKit and v8
is available on iOS. So is there any difference between them and extensions?

[droger, 2014/09/16 08:01:58]

As I understand, the dependencies go like this:

extensions
component
v8

That is, components can depends on v8, and extensions depend on components.

I'm saying this because I had gyp errors (circular dependencies) when I tried to
have the component depend on extensions.
We can also see in extension/DEPS and extensions/extensions.gyp that extensions
depend on several components.

That said, I am really unfamiliar with extensions, so if you are sure that it is
ok for a component to depend on extensions, then I can try again and see if I
can resolve the circular dependencies.

 ]