Separate Custom Element resolution and upgrade/createdCallback.

Separate Custom Element resolution and upgrade/createdCallback.

r164309 made Custom Element resolution (searching for a Custom Element
definition, and associating it with an element if there was a match)
immediately start the upgrade process. This is infelicitous because it
changed the timing of the createdCallback in some cases.

r164309 added the useful idea of "resolution" as a distinct step that
can be deferred. This change refines the integration of HTML Imports
and Custom Elements callback timing by separating resolution and
upgrade. Now HTML Imports can apply the brakes to resolution without
affecting which upgrades happen as a batch.

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

[dominicc (has gone to gerrit), 2014-01-31 07:55:18]

PTAL

[dglazkov, 2014-01-31 18:18:22]

lgtm

[dominicc (has gone to gerrit), 2014-02-03 01:15:48]

The CQ bit was checked by dominicc@chromium.org

[commit-bot: I haz the power, 2014-02-03 01:16:00]

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

[commit-bot: I haz the power, 2014-02-03 03:29:38]

Change committed as 166280

[commit-bot: I haz the power, 2014-02-03 03:29:44]

CQ bit was unchecked on CL. Ignoring.

[commit-bot: I haz the power, 2014-02-03 03:29:46]

CQ bit was unchecked on CL. Ignoring.

[commit-bot: I haz the power, 2014-02-03 03:29:47]

CQ bit was unchecked on CL. Ignoring.