Move the WebContents to the AsyncTabCreationParams for tabbed mode

Move the WebContents to the AsyncTabCreationParams for tabbed mode

* ChromeTabCreator (in tabbed mode) may now receive
  AsyncTabCreationParams with a WebContents inside.

* Mechanisms for passing WebContents to ChromeTabbedActivity
  from WebappActivity/DocumentActivity via Intents are
  removed.  Other parameters will eventually follow.

* Changes a WebappModeTest slightly to check for exact
  Tab IDs again.  Doesn't need to be inexact, anymore.

* Smushes together two methods in TabDelegate for creating new
  tabs.  They're supposed to be doing something similar, anyway.

BUG=508333, 508221
Committed: https://crrev.com/c13bdd545cd70260f86341c3d5a17ec756975f11
Cr-Commit-Position: refs/heads/master@{#339167}

[gone, 2015-07-15 22:48:28]

dfalcantara@chromium.org changed reviewers:
+ dtrainor@chromium.org

[gone, 2015-07-16 00:30:26]

Smashed a second CL on top of this one that does more cleaning/consolidation. 
Not sure if TabDelegate can shrink much more.

[David Trainor- moved to gerrit, 2015-07-16 21:32:18]

lgtm.  Although we might want to use a builder for creation of the
AsyncTabCreateParams instead.

https://chromiumcodereview.appspot.com/1238053002/diff/20001/chrome/android/j...
File
chrome/android/java/src/org/chromium/chrome/browser/tabmodel/document/TabDelegate.java
(right):

https://chromiumcodereview.appspot.com/1238053002/diff/20001/chrome/android/j...
chrome/android/java/src/org/chromium/chrome/browser/tabmodel/document/TabDelegate.java:86:
AsyncTabCreationParams asyncParams =
We should probably move this to the builder paradigm if we have that many
constructors.

[gone, 2015-07-16 22:05:50]

https://chromiumcodereview.appspot.com/1238053002/diff/20001/chrome/android/j...
File
chrome/android/java/src/org/chromium/chrome/browser/tabmodel/document/TabDelegate.java
(right):

https://chromiumcodereview.appspot.com/1238053002/diff/20001/chrome/android/j...
chrome/android/java/src/org/chromium/chrome/browser/tabmodel/document/TabDelegate.java:86:
AsyncTabCreationParams asyncParams =
On 2015/07/16 21:32:18, David Trainor wrote:
> We should probably move this to the builder paradigm if we have that many
> constructors.

Was made this way specifically to prevent setting incompatible parameters,
actually (they all get funneled to an assert block).  If you feel strongly about
it we can switch in a CL that touches the AsyncTabCreationParams.

[gone, 2015-07-16 22:05:54]

The CQ bit was checked by dfalcantara@chromium.org

[commit-bot: I haz the power, 2015-07-16 22:06:39]

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

[commit-bot: I haz the power, 2015-07-16 22:39:33]

The CQ bit was unchecked by commit-bot@chromium.org

[commit-bot: I haz the power, 2015-07-16 22:39:35]

Try jobs failed on following builders:
  android_clang_dbg_recipe on tryserver.chromium.linux (JOB_FAILED,
http://build.chromium.org/p/tryserver.chromium.linux/builders/android_clang_d...)

[gone, 2015-07-16 22:43:40]

The CQ bit was checked by dfalcantara@chromium.org

[gone, 2015-07-16 22:43:41]

The patchset sent to the CQ was uploaded after l-g-t-m from
dtrainor@chromium.org
Link to the patchset: https://codereview.chromium.org/1238053002/#ps40001
(title: "Findbugs")

[commit-bot: I haz the power, 2015-07-16 22:47:23]

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

[commit-bot: I haz the power, 2015-07-16 23:33:47]

Committed patchset #3 (id:40001)

[commit-bot: I haz the power, 2015-07-16 23:34:45]

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