Added chrome switch that lets tests override URL path, moved GAIA auth extension from CrOS

chrome/browser/resources/chromeos/login/oobe_screen_oauth_enrollment.js

Index: chrome/browser/resources/chromeos/login/oobe_screen_oauth_enrollment.js
diff --git a/chrome/browser/resources/chromeos/login/oobe_screen_oauth_enrollment.js b/chrome/browser/resources/chromeos/login/oobe_screen_oauth_enrollment.js
index 877713063aeaacf62d30e3ec2f6d2d1bea588aad..2c0a6df0e63aed791ccdf859d1d045818b7e4cb3 100644
--- a/chrome/browser/resources/chromeos/login/oobe_screen_oauth_enrollment.js
+++ b/chrome/browser/resources/chromeos/login/oobe_screen_oauth_enrollment.js
@@ -184,8 +184,9 @@ cr.define('oobe', function() {
      */
     onBeforeShow: function(data) {
       var url = data.signin_url;
-      if (data.gaiaOrigin)

[Nikita (slow), 2012/05/25 19:37:17]

Why this check was removed?
Still exists in screen_gaia_signin.js

[xiyuan, 2012/05/25 20:03:12]

If data.gaiaOrigin is missing, we actually would create a bad URL as the "?"
would be missing. Since it is working fine, I guess data.gaiaOrigin must always
exist.

Otherwise, think we should do the same trick as in screen_gaia_signin.js, i.e.
create a param list and join it later with "&" and decide whether a "?" is
needed at that time.

[zel, 2012/05/25 20:13:46]

Yes, this param exists always.

-        url += '?gaiaOrigin=' + encodeURIComponent(data.gaiaOrigin);
+      url += '?gaiaOrigin=' + encodeURIComponent(data.gaiaOrigin);
+      if (data.gaiaUrlBase)
+        url += '&gaiaUrlPath=' + encodeURIComponent(data.gaiaUrlPath);
       if (data.test_email) {
         url += '&test_email=' + encodeURIComponent(data.test_email);
         url += '&test_password=' + encodeURIComponent(data.test_password);