Move StyleResolver and related classes to core/css/resolver

Move StyleResolver and related classes to core/css/resolver

Move StyleResolver, ScopedStyleResolver, ViewportStyleResolver and
support classes to a new core/css/resolver directory.

Update include paths and build file as needed.

R=eseidel@chromium.org
BUG=239244
TESTED=No new tests, no change in functionality.

Committed: https://src.chromium.org/viewvc/blink?view=rev&revision=150003

[eseidel, 2013-05-09 03:57:30]

lgtm

So exciting!

[commit-bot: I haz the power, 2013-05-09 03:57:40]

CQ is trying da patch. Follow status at
https://chromium-status.appspot.com/cq/eae@chromium.org/15072003/9002

[eseidel, 2013-05-09 03:59:09]

I'm looking forward to seeing this subsystem develop.  I'm glad that you've
broken it off into its own folder, so that it's easier to tell what is part of
our internal CSS-cascade + style-building, vs. the CSSOM.

[commit-bot: I haz the power, 2013-05-09 04:01:18]

Change committed as 150003

[eseidel, 2013-05-09 04:03:18]

It's kinda disturbing how many files reach into this sub-system.  I suspect we
may want to consider splitting the "StyleResolver.h" front-end/API out into a
separate file which is at the top level of css or style, and then all the rest
of this exists in this resolver/ directory as support for that (small) API. 
We'll see how this evolves over the coming months.  I don't feel like I have
enough context to evaluate that design decision at this time. :)

[kenneth.r.christiansen, 2013-05-09 09:42:58]

When moving files around please make sure to update WATCHERS

[eseidel, 2013-05-09 10:16:03]

We should just make a presubmit which checks the validity of watchers paths.