Revert of Use the new java_cpp_enum rule in content.

Revert of Use the new java_cpp_enum rule in content. (patchset #8 id:140001 of https://codereview.chromium.org/615893003/)

Reason for revert:
Fails to compile on several bots:

https://chromegw.corp.google.com/i/clank.tot/builders/clang-clankium-tot-builder/builds/56800/steps/compile/logs/stdio

First error:
FAILED: cd ../../clank/native/framework; python <snip ...>
../../../clank/java/apps/chrome/src/com/google/android/apps/chrome/webapps/FullScreenActivityTab.java:28: error: cannot find symbol
import org.chromium.content.common.TopControlsState;
                                  ^
  symbol:   class TopControlsState
  location: package org.chromium.content.common

Original issue's description:
> Use the new java_cpp_enum rule in content.
>
> This moves most of the generated Java enums under content/ to use the
> java_cpp_enum rule removing the need for keeping the enums in
> separate list files and the need for the .template files.
>
> BUG=405532, 351558
>
> Committed: https://crrev.com/7d5f0a581ba2f0e79b09ecbf6127ad453a861a96
> Cr-Commit-Position: refs/heads/master@{#297789}

TBR=jam@chromium.org,yfriedman@chromium.org,scottmg@chromium.org,jdduke@chromium.org,brettw@chromium.org,mkosiba@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=405532, 351558
Committed: https://crrev.com/949b6e5050c7a2ee2a894799db19ec325ba911ef
Cr-Commit-Position: refs/heads/master@{#297793}

[perezju, 2014-10-02 09:54:09]

Created Revert of Use the new java_cpp_enum rule in content.

[commit-bot: I haz the power, 2014-10-02 09:55:17]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/625543002/1

[commit-bot: I haz the power, 2014-10-02 09:55:19]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2014-10-02 09:55:20]

No LGTM from a valid reviewer yet. Only full committers are accepted.
Even if an LGTM may have been provided, it was from a non-committer or
a provisional committer, _not_ a full super star committer.
See http://www.chromium.org/getting-involved/become-a-committer
Note that this has nothing to do with OWNERS files.

[Sami, 2014-10-02 10:04:35]

skyostil@chromium.org changed reviewers:
+ skyostil@chromium.org

[Sami, 2014-10-02 10:04:36]

lgtm.

[perezju, 2014-10-02 10:04:53]

The CQ bit was checked by perezju@chromium.org

[commit-bot: I haz the power, 2014-10-02 10:05:16]

CQ is trying da patch. Follow status at
 https://chromium-cq-status.appspot.com/patch-status/625543002/1

[commit-bot: I haz the power, 2014-10-02 10:06:04]

Committed patchset #1 (id:1) as 0fcbcf848c0abd7d7c04d8f71b12583682de1c16

[commit-bot: I haz the power, 2014-10-02 10:06:37]

Patchset 1 (id:??) landed as
https://crrev.com/949b6e5050c7a2ee2a894799db19ec325ba911ef
Cr-Commit-Position: refs/heads/master@{#297793}

[Sami, 2014-10-02 10:08:02]

A revert of this CL (patchset #1 id:1) has been created in
https://codereview.chromium.org/617103007/ by skyostil@chromium.org.

The reason for reverting is: Oops, wasn't supposed to revert this after all..

[mkosiba (inactive), 2014-10-02 10:14:19]

Regardless of the fact that I submitted a fix for clank immediately after this
CL landed
you should not revert upstream changes just because they break a hidden
repository.
Clank is not public, it's not possible for all of the Chromium committers to fix
it up,
if a Chromium change breaks it you should fix Clank, not revert Chromium
changes.