Deleting the forwarding header files base/debug/trace_event*

Deleting the forwarding header files base/debug/trace_event*

Now that the migration of the tracing files is completed and all the
tracing clients have been updated to point to base/trace_event/,
it is safe to remove the forwarding headers from the old location.
The only purpose of those headers, in fact, was to handle the renames
in smaller CLs.
The only thing left, at this point, is gradually renaming the
namespaces, which is going to be handled in the upcoming CLs.

See crrev.com/837303004 and the related bug for motivations.

BUG=451032
TBR=jam@chromium.org,sky@chromium.org

Committed: https://crrev.com/74a89f06ec7db49e1262847d4aba07ed87fd5930
Cr-Commit-Position: refs/heads/master@{#314357}

[ssid, 2015-02-03 12:55:13]

ssid@chromium.org changed reviewers:
+ picksi@chromium.org, primiano@chromium.org

[ssid, 2015-02-03 12:55:14]

This is CL for deleting the old files.

[Primiano Tucci (use gerrit), 2015-02-03 14:35:10]

LGTM, just one comment.

Please reword the description of the CL (the title is fine). This is NOT a
mechanical CL, just a clean up pass. 
I suggest something like:

Now that the migration of the tracing files is completed and all the
tracing clients have been updated to point to base/trace_event/,
it is safe to remove the forwarding headers from the old location.
The only purpose of those headers, in fact, was to handle the renames
in smaller CLs.
The only thing left, at this point, is gradually renaming the
namespaces, which is going to be handled in the upcoming CLs.

See crrev.com/837303004 and the related bug for motivations.

BUG=451032

https://codereview.chromium.org/897663002/diff/1/content/renderer/scheduler/t...
File content/renderer/scheduler/task_queue_manager.cc (left):

https://codereview.chromium.org/897663002/diff/1/content/renderer/scheduler/t...
content/renderer/scheduler/task_queue_manager.cc:8: #include
"base/debug/trace_event.h"
Just adding some context for the OWNERS (no action required by ssid@): these
lines were accidentally pulled in by an unrelated revert happened today (Feb 2)
in crrev.com/894183002. I guess the author of that CL messed them up the rebase.

[Primiano Tucci (use gerrit), 2015-02-03 17:11:55]

primiano@chromium.org changed reviewers:
+ danakj@chromium.org

[Primiano Tucci (use gerrit), 2015-02-03 17:11:55]

Dana, this is just a small cleanup. Can you PTAL?
The files have been moved and we want to remove the forwarding headers before
somebody regresses on this again.
Thanks

[danakj, 2015-02-03 17:18:33]

lgtm

[Primiano Tucci (use gerrit), 2015-02-03 17:22:13]

TBRing jam and sky for four diff lines  in content, ipc and ui.
probably not worth your time even clicking on this. This is just removing lines
which have been accidentally added during a wrong rebase of an unrelated revert
(crrev.com/837303004)

[Primiano Tucci (use gerrit), 2015-02-03 17:22:18]

The CQ bit was checked by primiano@chromium.org

[commit-bot: I haz the power, 2015-02-03 17:22:34]

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

[commit-bot: I haz the power, 2015-02-03 17:25:33]

Committed patchset #1 (id:1)

[commit-bot: I haz the power, 2015-02-03 17:26:30]

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