Revert of Move some sync/notifier to components/invalidation

Revert of Move some sync/notifier to components/invalidation (https://codereview.chromium.org/294123004/)

Reason for revert:
Passed the CQ but broke the buildbot.

Original issue's description:
> Move some sync/notifier to components/invalidation
> 
> Moves many of the files in sync/notifier to components/invalidation.
> 
> This change does not introduce any new dependencies.  The relevant
> dependency rules both before and after this change should be:
> - chrome/browser/invalidation and chrome in general depend on
>   components/invalidation.
> - components/invalidation depends on sync/notifier and sync in
>   general.
> - sync/notifier, components/invalidation, and various parts of
>   chrome all depend on sync/internal_api/public.
> 
> The eventual goal is to move all of sync/notifier into
> components/invalidation.  The invalidation-related parts of
> sync/internal_api/public should be moved to components/invalidation,
> too.  This will allow us to remove the deopendencies from
> components/invalidation to sync, and remove sync's dependencies on
> cacheinvalidation and libjingle.
> 
> This change is a regression in terms of shared library componentization.
> the files in the sync/notifier folder could be built as a shared
> library.  The files in compononents/invalidation do not support this
> yet.  The SYNC_EXPORT declarations in the moved files have been changed
> to INVALIDATION_EXPORT so as to not lose this information, but the
> macros are currently #defined to no-ops.
> 
> This change does not attempt to rename any classes or namespaces.
> Many of the files ported from sync/notifier still use the syncer
> namespace.  Some, like SyncSystemResources, still have names tied
> to their sync heritage.  This will be addressed in future CLs.
> 
> Some non-trivial or non-obvious changes include:
> - invalidator_state.h was moved to sync/internal_api/public/base so it
> could be shared by both sync/ and components/invalidation.  This should
> be fixed in a future CL.
> - FromNotifierReason was split out of invalidator_state.h and moved to
> the newly-created components/invalidator_reason_util.h
> 
> TBR=zea,rtenneti,mallinath,dcheng
> BUG=259559
> 
> Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=274350

TBR=pavely@chromium.org,dcheng@chromium.org,zea@chromium.org,rtenneti@chromium.org,mallinath@chromium.org,maniscalco@chromium.org
NOTREECHECKS=true
NOTRY=true
BUG=259559
Committed: https://src.chromium.org/viewvc/chrome?view=rev&revision=274364

[rlarocque, 2014-06-02 23:13:38]

Created Revert of Move some sync/notifier to components/invalidation

[commit-bot: I haz the power, 2014-06-02 23:14:33]

CQ is trying da patch. Follow status at
 https://chromium-status.appspot.com/cq/rlarocque@chromium.org/308413002/1

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

Change committed as 274364

[rlarocque, 2014-06-02 23:23:14]

On 2014/06/02 23:16:37, I haz the power (commit-bot) wrote:
> Change committed as 274364

FYI, the reason this got through the CQ probably has something to do with issue
376621.

Since I don't have a Win setup locally to try out fixes, I might have to wait
until it's fixed before I try to re-land.  If that takes a while, I can try to
look for a work-around, but it's probably easier to just wait.