Revert of Roll DEPS to class-dump 3.5

Revert of Roll DEPS to class-dump 3.5 (patchset #4 id:60001 of https://codereview.chromium.org/1106993002/)

Reason for revert:
Breaking https://build.chromium.org/p/chromium.mac/builders/iOS_Device/builds/7076

Original issue's description:
> Roll DEPS to class-dump 3.5
>
> Removes some build warnings.
>
> Moves the class-dump repo to a github auto-mirror instead of a mirror
> that needs to be manually updated.
>
> This also requires that the class-dump.gyp file move from the
> third-party repo into the main source tree. Note that the file
> structure of the class-dump source changed so the .gyp had to be
> updated. For comparison, the old .class-dump.gyp can be found at
> https://chromium.googlesource.com/chromium/deps/class-dump/+/master/class-dump.gyp
>
> BUG=318160
>
> Committed: https://crrev.com/1c80791ce7c29a29fc816d89d1a5fa2ac6503b3e
> Cr-Commit-Position: refs/heads/master@{#330798}

TBR=justincohen@chromium.org,rohitrao@chromium.org,lliabraa@chromium.org
NOPRESUBMIT=true
NOTREECHECKS=true
NOTRY=true
BUG=318160
Committed: https://crrev.com/b9d760ae212ab40c630a7c68e9eb27bae3bfab7a
Cr-Commit-Position: refs/heads/master@{#330804}

[sgurun-gerrit only, 2015-05-20 21:16:20]

Created Revert of Roll DEPS to class-dump 3.5

[commit-bot: I haz the power, 2015-05-20 21:17:09]

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

[commit-bot: I haz the power, 2015-05-20 21:24:02]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-05-20 21:25:42]

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

[smut, 2015-05-20 21:41:41]

+cc stuartmorgan, jam: Original CL passed iOS's ninja try bots. Another entry
for https://goto.google.com/ninja-xcode-differences?

[stuartmorgan, 2015-05-20 21:50:19]

On 2015/05/20 21:41:41, smut wrote:
> +cc stuartmorgan, jam: Original CL passed iOS's ninja try bots. Another entry
> for https://goto.google.com/ninja-xcode-differences

I can't tell without knowing more about why it failed. Did we somehow apply
chromium_code settings to the target?